com.sap.cloud.sdk.s4hana.datamodel.odata.services

Interface ConditionTypeForPricingInPurchasingService

All Superinterfaces:

BatchService<ConditionTypeForPricingInPurchasingServiceBatch>

All Known Implementing Classes:

DefaultConditionTypeForPricingInPurchasingService

public interface ConditionTypeForPricingInPurchasingService
extends BatchService<ConditionTypeForPricingInPurchasingServiceBatch>

This inbound service enables external applications to read data of condition types that are used for pricing in Purchasing. You can query each entity in this service to retrieve the corresponding business data.

Business Documentation

Reference: SAP API Business Hub

Details:

OData Service:	API_PURGPRICINGCONDITIONTYPE_SRV
API Version:	1
Communication Scenario:	Pricing Data Integration (SAP_COM_0294)
Scope Items:	Intercompany Processes - Project-Based Services (16T), Requisitioning (18J), Activity Management in Procurement (19C), Supplier Classification and Segmentation (19E), Sourcing with SAP Ariba Sourcing (1A0), Internal Project Management - Project-Based Services (1A8), Sales Rebate Processing (1B6), Credit Memo Processing (1EZ), Debit Memo Processing (1F1), Intercompany Sales Order Processing - Domestic (1HO), Sales Inquiry (1IQ), Customer Consignment (1IU), Advanced Available-to-Promise Processing (1JW), Advanced Resource Management - Project-Based Services (1KC), Supplier Quote Automation with SAP Ariba Commerce Automation (1L2), Invoice Processing by OpenText (1LE), Convergent Billing (1MC), Delivery Processing without Order Reference (1MI), Intercompany Sales Order Processing - International (1MX), Ariba - Sales Order to Invoice integration for SD (1NB), Extended Intercompany Processes for Sales (1WO), Request for Price (1XF), Digital Payments - Sales (1Z1), Accelerated Third-Party Returns (1Z3), External Billing (1Z6), Procure-to-Pay with SAP Ariba Buying and Invoicing (1ZM), Procurement of Services (22Z), Integration of Procurement with External Suppliers (2EJ), Integration of Sales with External Buyers (2EL), Sale of Services (2EQ), Sales Order Processing for Non-Stock Material (2ET), Intercompany Process for Customer Returns (2F4), Supplier Consignment (2LG), Automated Invoice Settlement (2LH), Basic Available-to-Promise Processing (2LN), Central Purchase Contracts (2ME), Basic Resource Management - Project-Based Services (2MV), Guided Buying Capability with SAP Ariba Buying (2NV), Scheduling Agreement for Subcontracting Procurement (2NX), Scheduling Agreement for Consignment Procurement (2NY), Cross-Company Purchasing Organization (2R3), Purchasing Rebate Processing (2R7), Sales Commissions - External Sales Representative (2TT), Complementary Procurement Functions (2TW), Procurement of Materials with Variant Configuration (2XU), Proposal of Material Group (2XV), Proposal of New Catalog Item (2XW), Sales Order Processing for Sales Kits (31Q), Service Order Management and Monitoring (3D2), Sales Processing using Third-Party with Shipping Notification (BD3), Sell from Stock (BD9), Free of Charge Delivery (BDA), Customer Returns (BDD), Sales Quotation (BDG), Sales Order Entry with One Time Customer (BDH), Sales Processing using Third-Party without Shipping Notification (BDK), Sales of Non-Stock Item with Order-Specific Procurement (BDN), Invoice Correction Process with Debit Memo (BDQ), Returnables Processing (BDW), Free Goods Processing (BKA), Sales Order Processing with Customer Down Payment (BKJ), Sales Order Fulfillment Monitoring (BKK), Invoice Correction Process with Credit Memo (BKL), Order-to-Cash Performance Monitoring (BKN), Accelerated Customer Returns (BKP), Sales Order Processing - SEPA Direct Debit Handling (BKX), Sales Order Processing with Invoice List and Collective Billing (BKZ), Purchase Contract (BMD), Return to Supplier (BMK), Scheduling Agreements in Procurement (BMR), Subcontracting (BMY), Consumable Purchasing (BNX), Sales Contract Management (I9I), Customer Project Management - Project-Based Services (J11), Time Recording - Project-Based Services (J12), Service and Material Procurement - Project-Based Services (J13), Sales Order Processing - Project-Based Services (J14), Procurement of Direct Materials (J45), Automated Purchase-to-Pay with SAP Ariba Commerce Automation (J82), Procurement of Direct Materials (O45), Supplier Evaluation and Performance Monitoring (SL4)
Authentication Methods:	Basic, x509
Business Object:	PurgPricingConditionRecord

Field Summary

Fields

Modifier and Type	Field and Description
static String	DEFAULT_SERVICE_PATH If no other path was provided via the withServicePath(String) method, this is the default service path used to access the endpoint.

Method Summary

Modifier and Type	Method and Description
PurgPrcgCndnTypeTextFluentHelper	getAllPurgPrcgCndnTypeText() Fetch multiple PurgPrcgCndnTypeText entities.
PurgPricingConditionTypeFluentHelper	getAllPurgPricingConditionType() Fetch multiple PurgPricingConditionType entities.
PurgPrcgCndnTypeTextByKeyFluentHelper	getPurgPrcgCndnTypeTextByKey(String language, String conditionUsage, String conditionApplication, String conditionType) Fetch a single PurgPrcgCndnTypeText entity using key fields.
PurgPricingConditionTypeByKeyFluentHelper	getPurgPricingConditionTypeByKey(String conditionUsage, String conditionApplication, String conditionType) Fetch a single PurgPricingConditionType entity using key fields.
ConditionTypeForPricingInPurchasingService	withServicePath(String servicePath) Overrides the default service path and returns a new service instance with the specified service path.

Methods inherited from interface com.sap.cloud.sdk.datamodel.odata.helper.batch.BatchService

batch

Field Detail

DEFAULT_SERVICE_PATH

static final String DEFAULT_SERVICE_PATH

If no other path was provided via the withServicePath(String) method, this is the default service path used to access the endpoint.

See Also:

Constant Field Values

Method Detail

withServicePath

@Nonnull
ConditionTypeForPricingInPurchasingService withServicePath(@Nonnull
                                                                    String servicePath)

Overrides the default service path and returns a new service instance with the specified service path. Also adjusts the respective entity URLs.

Parameters:

servicePath - Service path that will override the default.

Returns:

A new service instance with the specified service path.

getAllPurgPrcgCndnTypeText

@Nonnull
PurgPrcgCndnTypeTextFluentHelper getAllPurgPrcgCndnTypeText()

Fetch multiple PurgPrcgCndnTypeText entities.

Returns:

A fluent helper to fetch multiple PurgPrcgCndnTypeText entities. This fluent helper allows methods which modify the underlying query to be called before executing the query itself. To perform execution, call the execute method on the fluent helper object.

getPurgPrcgCndnTypeTextByKey

@Nonnull
PurgPrcgCndnTypeTextByKeyFluentHelper getPurgPrcgCndnTypeTextByKey(String language,
                                                                            String conditionUsage,
                                                                            String conditionApplication,
                                                                            String conditionType)

Fetch a single PurgPrcgCndnTypeText entity using key fields.

Parameters:

language - The language key indicates

Constraints: Not nullable, Maximum length: 2

conditionType - The condition type is used for different functions. In pricing, for example, the condition type lets you differentiate between different kinds of discount; in output determination, between different output types such as order confirmation or delivery note; in batch determination, between different strategy types.

Constraints: Not nullable, Maximum length: 4

conditionUsage - Determines for which area the condition is used (for example, pricing or output).

Constraints: Not nullable, Maximum length: 1

conditionApplication - Subdivides the usage of a condition (for example, pricing) for use in different application areas (for example, sales & distribution or purchasing).

Constraints: Not nullable, Maximum length: 2

Returns:

A fluent helper to fetch a single PurgPrcgCndnTypeText entity using key fields. This fluent helper allows methods which modify the underlying query to be called before executing the query itself. To perform execution, call the execute method on the fluent helper object.

getAllPurgPricingConditionType

@Nonnull
PurgPricingConditionTypeFluentHelper getAllPurgPricingConditionType()

Fetch multiple PurgPricingConditionType entities.

Returns:

A fluent helper to fetch multiple PurgPricingConditionType entities. This fluent helper allows methods which modify the underlying query to be called before executing the query itself. To perform execution, call the execute method on the fluent helper object.

getPurgPricingConditionTypeByKey

@Nonnull
PurgPricingConditionTypeByKeyFluentHelper getPurgPricingConditionTypeByKey(String conditionUsage,
                                                                                    String conditionApplication,
                                                                                    String conditionType)

Fetch a single PurgPricingConditionType entity using key fields.

Parameters:

conditionType - The condition type is used for different functions. In pricing, for example, the condition type lets you differentiate between different kinds of discount; in output determination, between different output types such as order confirmation or delivery note; in batch determination, between different strategy types.

Constraints: Not nullable, Maximum length: 4

conditionUsage - Determines for which area the condition is used (for example, pricing or output).

Constraints: Not nullable, Maximum length: 1

conditionApplication - Subdivides the usage of a condition (for example, pricing) for use in different application areas (for example, sales & distribution or purchasing).

Constraints: Not nullable, Maximum length: 2

Returns:

A fluent helper to fetch a single PurgPricingConditionType entity using key fields. This fluent helper allows methods which modify the underlying query to be called before executing the query itself. To perform execution, call the execute method on the fluent helper object.