General path:

SPRO > Sales and Distribution > Basic Functions > Pricing

Pricing procedure with custom requirement, condition value formula and condition basis formula (Number >= 600):

.

.

What´s additional price condition and how to use it

What is it?

An additional price condition is a price condition that depends on another price condition that has been previously retrieved when pricing is carried out in sales documents.

How to use it: business case

There was recently a request in the forum on how to solve the following scenario:

A price condition should be determined only if another condition was determined by a specific key combination (customer and material). Then and only then, a discount, if exists, has also to be determined.

Although a posible solution sounds to abap coding, it can be solved by using additional conditions. Let see how.

Custo

We define our own pricing conditions, for example,  PRZJ (price) and ZZKA (discount)

Remarks:

Once created the additional pricing procedure (see below in the document), we´ll need to update the condition to add it in field PricingProc.

Access sequence has exclusive search.

Condition ZZKA

Remarks:

Athough we´re not creating records for this condition directly on VK11, we need to type in an access sequence (when pricing, system will use PRZJ condition access sequence to retrieve PRZJ and its linked ZZKA condition).

In our normal pricing procedure we must have defined both price conditions.

We need to define an additional pricing procedure that will be called automatically in case system determines price condition PRZJ.

This price procedure will contain only conditions PRZJ and ZZKA (in our example).

Now, once saved, we can update our condition PRZJ and type ZJPR00 in firld PricingProc as already stated before.

Funcional

Now we create a record for PRZJ condition in VK11 for customer-material. Once typed in condition value, we click on goto-condition supplements.

To add an additional condition, set the cursor in a blank line and we select from matchcode condition ZZJA and enter discount value. Now condition ZZJA is linked to condition PRZJ for this key combination (customer-material).

Remarks:

If we don´t want to apply this discount  for the combination of a specific customer and material, we just don´t add ZZKA condition here.

We create another price record PRZJ for key combination material but without condition suplements.

Test

We create a sales order and system will retrieve price for material (price 10 euros) and its condition supplement ZZJA (2% discount).

When selecting details of condition PRZJ or ZZJA, we can see that they´ve been determined together.

Now, we delete price record for customer-material and create a new sales order. Sytem retrieves price condition by material key combination and condition  supplement it´s not determined as per requirement.

Regards,

Hi All

This is how the Delivery lead time configuration can be achieved in sales Order since my route is getting determined at Sales Order level .

Route determination has been used to calculate back picking date from customer required delivery date.

1. Change sales document type to enable route determination

2. Click on Sales document type and required scheduling as below .

3.  Create new routes with delivery lead time in days

4.Transit duration in Days as below in Route creation.

5.Create transportation zones for shipping points and ship-to customers

6.Define T.zone

7.  Assign shipping points to transportation zones

8.See as the assignment below .

9.Setup route determination where you link departure country code and transport zone (shipping point) to destination (ship-to) departure country code and transport zone and route

10. Set up the route as below .

This document will explain necessary configurations required in SAP ECC for enabling Intercompany billing for material movements across the organization either for sales or for stock transfer.

We have following scenarios in an organization where inter-company billing is involved:

Direct Shipment to customer using Intercompany plant: Orders requiring direct shipment of product employs standard intercompany functionality, where the sales order header will reflect the Sales Area owning the sale to the end customer, and the specific line item in question will possess a source plant.  Items with intercompany plants should default a pick-from-stock item category that ultimately generates a delivery from which both an end customer and intercompany invoice will be created. 

Intercompany Stock Transport Orders: To replenish stock at VMI hubs or distribution plant, intercompany stock transport orders with delivery-related billing is employed. 

Intercompany Pricing and Billing: For all intercompany transactions, direct-ship and stock transport alike, billing will be initiated upon PGI of the delivery.  '

Pre-requisite Master Data:

1. Intercompany Customers master records must be extended to the selling sales areas.
2. Intercompany Vendor master records must exist in the purchasing orgs.
3. EDI customer partners must be created to represent each of the sales organizations (WE20).
4. EDI vendor partners must be created to represent each one of the company codes.

Intercompany Direct Shipments Configuration:

• OVVA—Assign customer number (Buying company) to the sales organization that it represents

Sales and DistributionBilling Intercompany Billing Define Internal Customer Number by Sales Organization

• OVV9—Assign Delivering plant to sales area that owns the intercompany sale:

Sales and Distribution Billing Intercompany Billing Assign Organizational Units by Plant

• OVX6—Assign Sourcing plants to buying sales organizations / distribution channels.

Enterprise StructureAssignmentSales and DistributionAssign Sales Organization – Distribution Channel - Plant

• OVV8—Define the order types that are relevant for intercompany billing.

Sales and DistributionBillingIntercompany BillingDefine Order Types for Intercompany Billing

Intercompany Stock Transport Orders:

• OMGN—Set up stock transport orders.

Materials ManagementPurchasingPurchase OrderSet up Stock Transport Orders

Assign Delivery Type/Checking:

Type = NB

Supplying Plant = XXX

Delivery Type = NLCC

Checking Rule = A

Purchasing Document Type:

Supplying Plant = XXX

Plant = XXX

Type = NB

Intercompany Pricing Configuration:

• VOK0—Create new pricing conditions

Sales and DistributionBasic Functions Pricing Define condition types

• V/08—Define intercompany pricing procedure: Intercompany pricing may be derived following different intercompoany methodology like Resale Minus or Cost Plus. Depending upon company's requirement, it may be configured.

Sales and Distribution Basic Functions PricingPricing controlDefine and assign pricing procedures

• OVKK—Set up pricing procedure determination for new intercompany pricing procedure for all intercompany billing document types

Sales and Distribution Basic Functions Pricing Pricing control Define and assign pricing procedures

Intercompany Billing & Postings Configuration:

• WEL1—Set up automatic postings to vendor accounts.

Sales and Distribution Billing Intercompany Billing Automatic Posting to vendor account.

Log Address = XXX XXXXXXXXXX

Company Code = XXX

Vendor = XXXXXXXX

• OBCA—Set up company code assignments for inbound EDI invoice.

Financial Accounting Accounts Receivable and Accounts Payable Business TransactionsIncoming Invoices/Credit Memos EDI Assign Company Code for EDI Incoming Invoice.

Partner Type = KU

Partner Number = XXXXX

Company Code = XXX

• OBCE—Enter posting parameters for EDI invoice receipt for intercompany vendors.

Financial Accounting Accounts Receivable and Accounts Payable Business TransactionsIncoming Invoices/Credit Memos EDI Enter Program Parameters for EDI Incoming Invoice.

Partner Type = LI

Partner Number = XXXXXX

Company Code = XXX

Indicators for Transfer:

Posting details:

G/L db.pstg ky = 40                         Invoice doc.type = RE     

G/L cr.pstng ky = 50                        Cred.memo doc.type = RA     

Vend.deb.pstng ky = 21                   Debit clearing acct = (blank)    

Vend.cred.pstng ky = 31                  Credit clearing acct = (blank)     

Tax-ex.tax code = XX

Standard Unit of Measure:

Standard unit = blank

• OBCB—Set up GL account determination for EDI invoice processing for intercompany vendors.

Financial Accounting Accounts Receivable and Accounts Payable Business Transactions Incoming Invoices/Credit Memos EDI Assign Company Code for EDI Incoming Invoice:

Partner Type = LI

Partner Number = XXXXXX

Company Code = XXX

Goods/Services No. = *

Goods/Services Number Details:

Goods/serv ID text  = (blank)

G/L account no. = XXXXXXX

Company Code = XXX

• OBCD—Set up tax determination for EDI invoice processing for intercompany vendors.

Financial Accounting Accounts Receivable and Accounts Payable Business Transactions Incoming Invoices/Credit Memos EDI Assign Tax Codes For EDI Procedures.

Apart from above configuration, one may require to maintain priding condition records, access sequence, AR output type to enable auto AP posting along with AR invoice posting.

Hi

From sales point of view there are different processes that how you are managing your freight. If you are delivering some physical goods by using some vehicle and paying its transportation cost to vednor then you can have various options or requirements that how this freight should be calculated and posted. It depends on management decision and their requirement that how do they want you to configure this in system. I am listing down some scenarios and in this document I am going to explain most simplest one and after this I'll move on to others in next documents.

1. Freight is being paid to vendor/transporter and you don't have transportation module implemented. You also create accrual/clearing entry for this.
2. Freight is being paid to vendor and you have transportation module implemented. You calculate freight automatically and post it to FI. Company pays this freight and bears the expense.
3. Freight is being paid to vendor and you have transportation module implemented. You calculate freight automatically and post it to FI. Comapny doens't pay this freight but charges to customers.
4. Company has it's own transportation vehicles and it doesn't pay freight to any vendor but calculates and charges this separately to customer.
5. Company pays freight to vendor and charge this freight to material price in plant to plant transfer under same company code. This freight is calculated in shipment cost document automatically.

There could be many other scenarios but by following these and by following the configuration which I am going to explain in these you would be able to cover up most of the scenarios.

In this document I'll be covering point number one only which is how to enter freight in delivery document and copy this to billing and post in FI with accrual entry. This accrual entry will be debiting freight expense and crediting freight payable liability which will be debited later on when we will pay to vendor.

Configuration steps.

While explaining these steps I assume that you are familiar with basic configuration steps and prcesses.

Create separate pricing procedure in V/08 with only one condition in it i.e. Freight Expense. This freight expense is basically an accrual condition and you have marked it as accrual in V/06 under control data 2. Condition class A and calculation type is C. This is manual condition and no need to maintain any access sequence. If you want to make it automatic then use access sequence and maintain condition record.

Assign this pricing procedure to your delivery type. For delivery types we can't determine pricing procedure like we do for orders or billing documents.

Now maintain E in pricing source for copy control from delivery to billing document in VTFL Tcode.

Configuration is completed and you can now test your scenario. I am listing down the steps that I did for its testing.

Created sale order with VA01.

Created delivery order with VL01N and entered freight charges at header level in delivery document because this freight is for complete delivery document.

Created invoice in VF01 and here you can see that freight charges have been copied from DO to billing document.

Posted invoice to FI with VF02 and in accounting document you can view that freight expense is with debit entry and freight accrual is with credit.

This is how we control freight with most simplest and easiest way. I will continue this document by explaining key points in other scenarios I have listed above. If you have some other scenario which I have not covered in these 5 listed scenarios then I would appreciate if you share that in comments section and I will try my level best to cover that too in this document.

Positive/negative feedback will help me to improve next documents.

Continued here. . .

Thank$

Business Requirement: Many times Business require to send certain output directly to external Id of customer, business partner etc. This document discuss those scenario.

I find in SDN some consultants asking this requirement, I hope this document will be helpful.

Here I will discuss solution which I implemeted in my  business process.

If you find this document helpful then please do not forget to LIKE this document . Please give your rating.

Advantage:  Solution can be use to send output to partner email Id. Consultant can enhance functionality based on logic written in routine , may use logic in routine to fetch data from Ztable which gives flexibility.

we are calling function module 'SO_NEW_DOCUMENT_SEND_API1' in this routine. This function module enables to send output to external email ID

Presetting: Basis setting  (Tcode SCOT) should be available to allow output to be sent to external email id. You may use SOSV or SOST to check this.

I consider all other standard settings of output like access , access sequence, routine are known to consultant and i will not discuss these setting here.

T Code: NACE

For sales order output select application V1 and then Click Output Type button:

If it is require to make this output condtion based on access then define access sequence and assign it to output (Standard SAP Access creation).

In Default view tab select:

Dispatch time as per your requirement.

Transmission Medium '5 External Send'

and partner function which require this output.

Now create and assign form routine to output along with print program

You can take help of ABAPER to create program as per your Prnt program and Form Routine.

Here Form Routine is controlling Email.

You can put logic here that how to fetch email Id, if there is any validation check etc.

In my case I am fetching email from HR Master T Code :PA30. Subtype Communication.

You may write your own logic to fetch email

Note: In this routine, we are calling function module 'SO_NEW_DOCUMENT_SEND_API1' . This function module enables to send document.

Now create output condtion record if this output has access sequence based determination.

Trigger output via sales order

T Code: VA01 : Header Output Screen

T Code: PA30, Info type 0105, Sub Type 0010

I have maintained my email ID in PA30, Info type Communication (0105) Sub Type 0010 (Email).

TCode : SOSV  To Check mail is going or not ( This will also require Basis Setting)

Mail is triggered to my external Email ID which is visible in SOSV.

Regards

Neeraj

General path:

SPRO > Sales and Distribution > Basic Functions > Pricing

Pricing procedure with custom requirement, condition value formula and condition basis formula (Number >= 600):

.

.

What´s additional price condition and how to use it

What is it?

An additional price condition is a price condition that depends on another price condition that has been previously retrieved when pricing is carried out in sales documents.

How to use it: business case

There was recently a request in the forum on how to solve the following scenario:

A price condition should be determined only if another condition was determined by a specific key combination (customer and material). Then and only then, a discount, if exists, has also to be determined.

Although a posible solution sounds to abap coding, it can be solved by using additional conditions. Let see how.

Custo

We define our own pricing conditions, for example,  PRZJ (price) and ZZKA (discount)

Remarks:

Once created the additional pricing procedure (see below in the document), we´ll need to update the condition to add it in field PricingProc.

Access sequence has exclusive search.

Condition ZZKA

Remarks:

Athough we´re not creating records for this condition directly on VK11, we need to type in an access sequence (when pricing, system will use PRZJ condition access sequence to retrieve PRZJ and its linked ZZKA condition).

In our normal pricing procedure we must have defined both price conditions.

We need to define an additional pricing procedure that will be called automatically in case system determines price condition PRZJ.

This price procedure will contain only conditions PRZJ and ZZKA (in our example).

Now, once saved, we can update our condition PRZJ and type ZJPR00 in firld PricingProc as already stated before.

Funcional

Now we create a record for PRZJ condition in VK11 for customer-material. Once typed in condition value, we click on goto-condition supplements.

To add an additional condition, set the cursor in a blank line and we select from matchcode condition ZZJA and enter discount value. Now condition ZZJA is linked to condition PRZJ for this key combination (customer-material).

Remarks:

If we don´t want to apply this discount  for the combination of a specific customer and material, we just don´t add ZZKA condition here.

We create another price record PRZJ for key combination material but without condition suplements.

Test

We create a sales order and system will retrieve price for material (price 10 euros) and its condition supplement ZZJA (2% discount).

When selecting details of condition PRZJ or ZZJA, we can see that they´ve been determined together.

Now, we delete price record for customer-material and create a new sales order. Sytem retrieves price condition by material key combination and condition  supplement it´s not determined as per requirement.

Regards,

Hi All

This is how the Delivery lead time configuration can be achieved in sales Order since my route is getting determined at Sales Order level .

Route determination has been used to calculate back picking date from customer required delivery date.

1. Change sales document type to enable route determination

2. Click on Sales document type and required scheduling as below .

3.  Create new routes with delivery lead time in days

4.Transit duration in Days as below in Route creation.

5.Create transportation zones for shipping points and ship-to customers

6.Define T.zone

7.  Assign shipping points to transportation zones

8.See as the assignment below .

9.Setup route determination where you link departure country code and transport zone (shipping point) to destination (ship-to) departure country code and transport zone and route

10. Set up the route as below .

This document will explain necessary configurations required in SAP ECC for enabling Intercompany billing for material movements across the organization either for sales or for stock transfer.

We have following scenarios in an organization where inter-company billing is involved:

Direct Shipment to customer using Intercompany plant: Orders requiring direct shipment of product employs standard intercompany functionality, where the sales order header will reflect the Sales Area owning the sale to the end customer, and the specific line item in question will possess a source plant.  Items with intercompany plants should default a pick-from-stock item category that ultimately generates a delivery from which both an end customer and intercompany invoice will be created. 

Intercompany Stock Transport Orders: To replenish stock at VMI hubs or distribution plant, intercompany stock transport orders with delivery-related billing is employed. 

Intercompany Pricing and Billing: For all intercompany transactions, direct-ship and stock transport alike, billing will be initiated upon PGI of the delivery.  '

Pre-requisite Master Data:

1. Intercompany Customers master records must be extended to the selling sales areas.
2. Intercompany Vendor master records must exist in the purchasing orgs.
3. EDI customer partners must be created to represent each of the sales organizations (WE20).
4. EDI vendor partners must be created to represent each one of the company codes.

Intercompany Direct Shipments Configuration:

• OVVA—Assign customer number (Buying company) to the sales organization that it represents

Sales and DistributionBilling Intercompany Billing Define Internal Customer Number by Sales Organization

• OVV9—Assign Delivering plant to sales area that owns the intercompany sale:

Sales and Distribution Billing Intercompany Billing Assign Organizational Units by Plant

• OVX6—Assign Sourcing plants to buying sales organizations / distribution channels.

Enterprise StructureAssignmentSales and DistributionAssign Sales Organization – Distribution Channel - Plant

• OVV8—Define the order types that are relevant for intercompany billing.

Sales and DistributionBillingIntercompany BillingDefine Order Types for Intercompany Billing

Intercompany Stock Transport Orders:

• OMGN—Set up stock transport orders.

Materials ManagementPurchasingPurchase OrderSet up Stock Transport Orders

Assign Delivery Type/Checking:

Type = NB

Supplying Plant = XXX

Delivery Type = NLCC

Checking Rule = A

Purchasing Document Type:

Supplying Plant = XXX

Plant = XXX

Type = NB

Intercompany Pricing Configuration:

• VOK0—Create new pricing conditions

Sales and DistributionBasic Functions Pricing Define condition types

• V/08—Define intercompany pricing procedure: Intercompany pricing may be derived following different intercompoany methodology like Resale Minus or Cost Plus. Depending upon company's requirement, it may be configured.

Sales and Distribution Basic Functions PricingPricing controlDefine and assign pricing procedures

• OVKK—Set up pricing procedure determination for new intercompany pricing procedure for all intercompany billing document types

Sales and Distribution Basic Functions Pricing Pricing control Define and assign pricing procedures

Intercompany Billing & Postings Configuration:

• WEL1—Set up automatic postings to vendor accounts.

Sales and Distribution Billing Intercompany Billing Automatic Posting to vendor account.

Log Address = XXX XXXXXXXXXX

Company Code = XXX

Vendor = XXXXXXXX

• OBCA—Set up company code assignments for inbound EDI invoice.

Financial Accounting Accounts Receivable and Accounts Payable Business TransactionsIncoming Invoices/Credit Memos EDI Assign Company Code for EDI Incoming Invoice.

Partner Type = KU

Partner Number = XXXXX

Company Code = XXX

• OBCE—Enter posting parameters for EDI invoice receipt for intercompany vendors.

Financial Accounting Accounts Receivable and Accounts Payable Business TransactionsIncoming Invoices/Credit Memos EDI Enter Program Parameters for EDI Incoming Invoice.

Partner Type = LI

Partner Number = XXXXXX

Company Code = XXX

Indicators for Transfer:

Posting details:

G/L db.pstg ky = 40                         Invoice doc.type = RE     

G/L cr.pstng ky = 50                        Cred.memo doc.type = RA     

Vend.deb.pstng ky = 21                   Debit clearing acct = (blank)    

Vend.cred.pstng ky = 31                  Credit clearing acct = (blank)     

Tax-ex.tax code = XX

Standard Unit of Measure:

Standard unit = blank

• OBCB—Set up GL account determination for EDI invoice processing for intercompany vendors.

Financial Accounting Accounts Receivable and Accounts Payable Business Transactions Incoming Invoices/Credit Memos EDI Assign Company Code for EDI Incoming Invoice:

Partner Type = LI

Partner Number = XXXXXX

Company Code = XXX

Goods/Services No. = *

Goods/Services Number Details:

Goods/serv ID text  = (blank)

G/L account no. = XXXXXXX

Company Code = XXX

• OBCD—Set up tax determination for EDI invoice processing for intercompany vendors.

Financial Accounting Accounts Receivable and Accounts Payable Business Transactions Incoming Invoices/Credit Memos EDI Assign Tax Codes For EDI Procedures.

Apart from above configuration, one may require to maintain priding condition records, access sequence, AR output type to enable auto AP posting along with AR invoice posting.

Hi

From sales point of view there are different processes that how you are managing your freight. If you are delivering some physical goods by using some vehicle and paying its transportation cost to vednor then you can have various options or requirements that how this freight should be calculated and posted. It depends on management decision and their requirement that how do they want you to configure this in system. I am listing down some scenarios and in this document I am going to explain most simplest one and after this I'll move on to others in next documents.

1. Freight is being paid to vendor/transporter and you don't have transportation module implemented. You also create accrual/clearing entry for this.
2. Freight is being paid to vendor and you have transportation module implemented. You calculate freight automatically and post it to FI. Company pays this freight and bears the expense.
3. Freight is being paid to vendor and you have transportation module implemented. You calculate freight automatically and post it to FI. Comapny doens't pay this freight but charges to customers.
4. Company has it's own transportation vehicles and it doesn't pay freight to any vendor but calculates and charges this separately to customer.
5. Company pays freight to vendor and charge this freight to material price in plant to plant transfer under same company code. This freight is calculated in shipment cost document automatically.

There could be many other scenarios but by following these and by following the configuration which I am going to explain in these you would be able to cover up most of the scenarios.

In this document I'll be covering point number one only which is how to enter freight in delivery document and copy this to billing and post in FI with accrual entry. This accrual entry will be debiting freight expense and crediting freight payable liability which will be debited later on when we will pay to vendor.

Configuration steps.

While explaining these steps I assume that you are familiar with basic configuration steps and prcesses.

Create separate pricing procedure in V/08 with only one condition in it i.e. Freight Expense. This freight expense is basically an accrual condition and you have marked it as accrual in V/06 under control data 2. Condition class A and calculation type is C. This is manual condition and no need to maintain any access sequence. If you want to make it automatic then use access sequence and maintain condition record.

Assign this pricing procedure to your delivery type. For delivery types we can't determine pricing procedure like we do for orders or billing documents.

Now maintain E in pricing source for copy control from delivery to billing document in VTFL Tcode.

Configuration is completed and you can now test your scenario. I am listing down the steps that I did for its testing.

Created sale order with VA01.

Created delivery order with VL01N and entered freight charges at header level in delivery document because this freight is for complete delivery document.

Created invoice in VF01 and here you can see that freight charges have been copied from DO to billing document.

Posted invoice to FI with VF02 and in accounting document you can view that freight expense is with debit entry and freight accrual is with credit.

This is how we control freight with most simplest and easiest way. I will continue this document by explaining key points in other scenarios I have listed above. If you have some other scenario which I have not covered in these 5 listed scenarios then I would appreciate if you share that in comments section and I will try my level best to cover that too in this document.

Positive/negative feedback will help me to improve next documents.

Continued here. . .

Thank$

Business Requirement: Many times Business require to send certain output directly to external Id of customer, business partner etc. This document discuss those scenario.

I find in SDN some consultants asking this requirement, I hope this document will be helpful.

Here I will discuss solution which I implemeted in my  business process.

If you find this document helpful then please do not forget to LIKE this document . Please give your rating.

Advantage:  Solution can be use to send output to partner email Id. Consultant can enhance functionality based on logic written in routine , may use logic in routine to fetch data from Ztable which gives flexibility.

we are calling function module 'SO_NEW_DOCUMENT_SEND_API1' in this routine. This function module enables to send output to external email ID

Presetting: Basis setting  (Tcode SCOT) should be available to allow output to be sent to external email id. You may use SOSV or SOST to check this.

I consider all other standard settings of output like access , access sequence, routine are known to consultant and i will not discuss these setting here.

T Code: NACE

For sales order output select application V1 and then Click Output Type button:

If it is require to make this output condtion based on access then define access sequence and assign it to output (Standard SAP Access creation).

In Default view tab select:

Dispatch time as per your requirement.

Transmission Medium '5 External Send'

and partner function which require this output.

Now create and assign form routine to output along with print program

You can take help of ABAPER to create program as per your Prnt program and Form Routine.

Here Form Routine is controlling Email.

You can put logic here that how to fetch email Id, if there is any validation check etc.

In my case I am fetching email from HR Master T Code :PA30. Subtype Communication.

You may write your own logic to fetch email

Note: In this routine, we are calling function module 'SO_NEW_DOCUMENT_SEND_API1' . This function module enables to send document.

Now create output condtion record if this output has access sequence based determination.

Trigger output via sales order

T Code: VA01 : Header Output Screen

T Code: PA30, Info type 0105, Sub Type 0010

I have maintained my email ID in PA30, Info type Communication (0105) Sub Type 0010 (Email).

TCode : SOSV  To Check mail is going or not ( This will also require Basis Setting)

Mail is triggered to my external Email ID which is visible in SOSV.

Regards

Neeraj

General path:

SPRO > Sales and Distribution > Basic Functions > Pricing

Pricing procedure with custom requirement, condition value formula and condition basis formula (Number >= 600):

.

.

What´s additional price condition and how to use it

What is it?

An additional price condition is a price condition that depends on another price condition that has been previously retrieved when pricing is carried out in sales documents.

How to use it: business case

There was recently a request in the forum on how to solve the following scenario:

A price condition should be determined only if another condition was determined by a specific key combination (customer and material). Then and only then, a discount, if exists, has also to be determined.

Although a posible solution sounds to abap coding, it can be solved by using additional conditions. Let see how.

Custo

We define our own pricing conditions, for example,  PRZJ (price) and ZZKA (discount)

Remarks:

Once created the additional pricing procedure (see below in the document), we´ll need to update the condition to add it in field PricingProc.

Access sequence has exclusive search.

Condition ZZKA

Remarks:

Athough we´re not creating records for this condition directly on VK11, we need to type in an access sequence (when pricing, system will use PRZJ condition access sequence to retrieve PRZJ and its linked ZZKA condition).

In our normal pricing procedure we must have defined both price conditions.

We need to define an additional pricing procedure that will be called automatically in case system determines price condition PRZJ.

This price procedure will contain only conditions PRZJ and ZZKA (in our example).

Now, once saved, we can update our condition PRZJ and type ZJPR00 in firld PricingProc as already stated before.

Funcional

Now we create a record for PRZJ condition in VK11 for customer-material. Once typed in condition value, we click on goto-condition supplements.

To add an additional condition, set the cursor in a blank line and we select from matchcode condition ZZJA and enter discount value. Now condition ZZJA is linked to condition PRZJ for this key combination (customer-material).

Remarks:

If we don´t want to apply this discount  for the combination of a specific customer and material, we just don´t add ZZKA condition here.

We create another price record PRZJ for key combination material but without condition suplements.

Test

We create a sales order and system will retrieve price for material (price 10 euros) and its condition supplement ZZJA (2% discount).

When selecting details of condition PRZJ or ZZJA, we can see that they´ve been determined together.

Now, we delete price record for customer-material and create a new sales order. Sytem retrieves price condition by material key combination and condition  supplement it´s not determined as per requirement.

Regards,

Hi All

This is how the Delivery lead time configuration can be achieved in sales Order since my route is getting determined at Sales Order level .

Route determination has been used to calculate back picking date from customer required delivery date.

1. Change sales document type to enable route determination

2. Click on Sales document type and required scheduling as below .

3.  Create new routes with delivery lead time in days

4.Transit duration in Days as below in Route creation.

5.Create transportation zones for shipping points and ship-to customers

6.Define T.zone

7.  Assign shipping points to transportation zones

8.See as the assignment below .

9.Setup route determination where you link departure country code and transport zone (shipping point) to destination (ship-to) departure country code and transport zone and route

10. Set up the route as below .

This document will explain necessary configurations required in SAP ECC for enabling Intercompany billing for material movements across the organization either for sales or for stock transfer.

We have following scenarios in an organization where inter-company billing is involved:

Direct Shipment to customer using Intercompany plant: Orders requiring direct shipment of product employs standard intercompany functionality, where the sales order header will reflect the Sales Area owning the sale to the end customer, and the specific line item in question will possess a source plant.  Items with intercompany plants should default a pick-from-stock item category that ultimately generates a delivery from which both an end customer and intercompany invoice will be created. 

Intercompany Stock Transport Orders: To replenish stock at VMI hubs or distribution plant, intercompany stock transport orders with delivery-related billing is employed. 

Intercompany Pricing and Billing: For all intercompany transactions, direct-ship and stock transport alike, billing will be initiated upon PGI of the delivery.  '

Pre-requisite Master Data:

1. Intercompany Customers master records must be extended to the selling sales areas.
2. Intercompany Vendor master records must exist in the purchasing orgs.
3. EDI customer partners must be created to represent each of the sales organizations (WE20).
4. EDI vendor partners must be created to represent each one of the company codes.

Intercompany Direct Shipments Configuration:

• OVVA—Assign customer number (Buying company) to the sales organization that it represents

Sales and DistributionBilling Intercompany Billing Define Internal Customer Number by Sales Organization

• OVV9—Assign Delivering plant to sales area that owns the intercompany sale:

Sales and Distribution Billing Intercompany Billing Assign Organizational Units by Plant

• OVX6—Assign Sourcing plants to buying sales organizations / distribution channels.

Enterprise StructureAssignmentSales and DistributionAssign Sales Organization – Distribution Channel - Plant

• OVV8—Define the order types that are relevant for intercompany billing.

Sales and DistributionBillingIntercompany BillingDefine Order Types for Intercompany Billing

Intercompany Stock Transport Orders:

• OMGN—Set up stock transport orders.

Materials ManagementPurchasingPurchase OrderSet up Stock Transport Orders

Assign Delivery Type/Checking:

Type = NB

Supplying Plant = XXX

Delivery Type = NLCC

Checking Rule = A

Purchasing Document Type:

Supplying Plant = XXX

Plant = XXX

Type = NB

Intercompany Pricing Configuration:

• VOK0—Create new pricing conditions

Sales and DistributionBasic Functions Pricing Define condition types

• V/08—Define intercompany pricing procedure: Intercompany pricing may be derived following different intercompoany methodology like Resale Minus or Cost Plus. Depending upon company's requirement, it may be configured.

Sales and Distribution Basic Functions PricingPricing controlDefine and assign pricing procedures

• OVKK—Set up pricing procedure determination for new intercompany pricing procedure for all intercompany billing document types

Sales and Distribution Basic Functions Pricing Pricing control Define and assign pricing procedures

Intercompany Billing & Postings Configuration:

• WEL1—Set up automatic postings to vendor accounts.

Sales and Distribution Billing Intercompany Billing Automatic Posting to vendor account.

Log Address = XXX XXXXXXXXXX

Company Code = XXX

Vendor = XXXXXXXX

• OBCA—Set up company code assignments for inbound EDI invoice.

Financial Accounting Accounts Receivable and Accounts Payable Business TransactionsIncoming Invoices/Credit Memos EDI Assign Company Code for EDI Incoming Invoice.

Partner Type = KU

Partner Number = XXXXX

Company Code = XXX

• OBCE—Enter posting parameters for EDI invoice receipt for intercompany vendors.

Financial Accounting Accounts Receivable and Accounts Payable Business TransactionsIncoming Invoices/Credit Memos EDI Enter Program Parameters for EDI Incoming Invoice.

Partner Type = LI

Partner Number = XXXXXX

Company Code = XXX

Indicators for Transfer:

Posting details:

G/L db.pstg ky = 40                         Invoice doc.type = RE     

G/L cr.pstng ky = 50                        Cred.memo doc.type = RA     

Vend.deb.pstng ky = 21                   Debit clearing acct = (blank)    

Vend.cred.pstng ky = 31                  Credit clearing acct = (blank)     

Tax-ex.tax code = XX

Standard Unit of Measure:

Standard unit = blank

• OBCB—Set up GL account determination for EDI invoice processing for intercompany vendors.

Financial Accounting Accounts Receivable and Accounts Payable Business Transactions Incoming Invoices/Credit Memos EDI Assign Company Code for EDI Incoming Invoice:

Partner Type = LI

Partner Number = XXXXXX

Company Code = XXX

Goods/Services No. = *

Goods/Services Number Details:

Goods/serv ID text  = (blank)

G/L account no. = XXXXXXX

Company Code = XXX

• OBCD—Set up tax determination for EDI invoice processing for intercompany vendors.

Financial Accounting Accounts Receivable and Accounts Payable Business Transactions Incoming Invoices/Credit Memos EDI Assign Tax Codes For EDI Procedures.

Apart from above configuration, one may require to maintain priding condition records, access sequence, AR output type to enable auto AP posting along with AR invoice posting.

Hi

From sales point of view there are different processes that how you are managing your freight. If you are delivering some physical goods by using some vehicle and paying its transportation cost to vednor then you can have various options or requirements that how this freight should be calculated and posted. It depends on management decision and their requirement that how do they want you to configure this in system. I am listing down some scenarios and in this document I am going to explain most simplest one and after this I'll move on to others in next documents.

1. Freight is being paid to vendor/transporter and you don't have transportation module implemented. You also create accrual/clearing entry for this.
2. Freight is being paid to vendor and you have transportation module implemented. You calculate freight automatically and post it to FI. Company pays this freight and bears the expense.
3. Freight is being paid to vendor and you have transportation module implemented. You calculate freight automatically and post it to FI. Comapny doens't pay this freight but charges to customers.
4. Company has it's own transportation vehicles and it doesn't pay freight to any vendor but calculates and charges this separately to customer.
5. Company pays freight to vendor and charge this freight to material price in plant to plant transfer under same company code. This freight is calculated in shipment cost document automatically.

There could be many other scenarios but by following these and by following the configuration which I am going to explain in these you would be able to cover up most of the scenarios.

In this document I'll be covering point number one only which is how to enter freight in delivery document and copy this to billing and post in FI with accrual entry. This accrual entry will be debiting freight expense and crediting freight payable liability which will be debited later on when we will pay to vendor.

Configuration steps.

While explaining these steps I assume that you are familiar with basic configuration steps and prcesses.

Create separate pricing procedure in V/08 with only one condition in it i.e. Freight Expense. This freight expense is basically an accrual condition and you have marked it as accrual in V/06 under control data 2. Condition class A and calculation type is C. This is manual condition and no need to maintain any access sequence. If you want to make it automatic then use access sequence and maintain condition record.

Assign this pricing procedure to your delivery type. For delivery types we can't determine pricing procedure like we do for orders or billing documents.

Now maintain E in pricing source for copy control from delivery to billing document in VTFL Tcode.

Configuration is completed and you can now test your scenario. I am listing down the steps that I did for its testing.

Created sale order with VA01.

Created delivery order with VL01N and entered freight charges at header level in delivery document because this freight is for complete delivery document.

Created invoice in VF01 and here you can see that freight charges have been copied from DO to billing document.

Posted invoice to FI with VF02 and in accounting document you can view that freight expense is with debit entry and freight accrual is with credit.

This is how we control freight with most simplest and easiest way. I will continue this document by explaining key points in other scenarios I have listed above. If you have some other scenario which I have not covered in these 5 listed scenarios then I would appreciate if you share that in comments section and I will try my level best to cover that too in this document.

Positive/negative feedback will help me to improve next documents.

Continued here. . .

Thank$

Business Requirement: Many times Business require to send certain output directly to external Id of customer, business partner etc. This document discuss those scenario.

I find in SDN some consultants asking this requirement, I hope this document will be helpful.

Here I will discuss solution which I implemeted in my  business process.

If you find this document helpful then please do not forget to LIKE this document . Please give your rating.

Advantage:  Solution can be use to send output to partner email Id. Consultant can enhance functionality based on logic written in routine , may use logic in routine to fetch data from Ztable which gives flexibility.

we are calling function module 'SO_NEW_DOCUMENT_SEND_API1' in this routine. This function module enables to send output to external email ID

Presetting: Basis setting  (Tcode SCOT) should be available to allow output to be sent to external email id. You may use SOSV or SOST to check this.

I consider all other standard settings of output like access , access sequence, routine are known to consultant and i will not discuss these setting here.

T Code: NACE

For sales order output select application V1 and then Click Output Type button:

If it is require to make this output condtion based on access then define access sequence and assign it to output (Standard SAP Access creation).

In Default view tab select:

Dispatch time as per your requirement.

Transmission Medium '5 External Send'

and partner function which require this output.

Now create and assign form routine to output along with print program

You can take help of ABAPER to create program as per your Prnt program and Form Routine.

Here Form Routine is controlling Email.

You can put logic here that how to fetch email Id, if there is any validation check etc.

In my case I am fetching email from HR Master T Code :PA30. Subtype Communication.

You may write your own logic to fetch email

Note: In this routine, we are calling function module 'SO_NEW_DOCUMENT_SEND_API1' . This function module enables to send document.

Now create output condtion record if this output has access sequence based determination.

Trigger output via sales order

T Code: VA01 : Header Output Screen

T Code: PA30, Info type 0105, Sub Type 0010

I have maintained my email ID in PA30, Info type Communication (0105) Sub Type 0010 (Email).

TCode : SOSV  To Check mail is going or not ( This will also require Basis Setting)

Mail is triggered to my external Email ID which is visible in SOSV.

Regards

Neeraj

Article: Approach for system and business process integration with EDI business partner along with the case study.

Summary: Article includes the case study for EDI integration helping companies to create system-to-system integration and seamless business processes.

Author: Kamal Dial

Created on: 18^st September 2014.

Author Bio: Kamal is a Consultant at Infosys and has over 4.5 years of professional work experience as business process and domain consultant. He is engineering graduate from PEC Chandigarh and post graduate in Management from Symbiosis Pune. He would like to thank his team member Amerjit Singh Mann for his valuable contribution and guidance towards this implementation.

Introduction- EDI integration for seamless business process continuity.

Integration between different business processes within an organization and across organizations is very important for a successful SAP implementation. Integration includes interfacing with legacy systems, communicating with third party partners, and integrating business processes across different systems. EDI (Electronic Data Interchange) technology is used for integration which uses IDOC (Intermediate Document) interface for exchanging data between different systems. EDI provides business process integration across companies by exchanging business documents such as sales order, order confirmation, delivery notes, shipment notices, invoices in electronic form using industry standard formats such as ANSI X12 and EDIFACT.

Purpose: Purpose of this integration with EDI partner is to optimize the business process and improve overall efficiency by eradicating manual intervention in the current process.

Case study: This case study is about major agribusiness client having high volume business with third party EDI partner which involves  exchanging information related to order management, order acknowledgment, availability, delivery, invoice. It required a B2B system integration using standardized communication process considering high transactional volume and inefficiencies in the current process.

As Is Business process

This B2B scenario involves exchange of various documents and information between business partners at different point of time. Usual steps involved as followed:

• Sales Order is placed by EDI business partner with sales representative executive of Agribusiness company using email as mode of communication.
• Data provided by EDI partner involves parameters like EAN code, Quantity required, sold to partner details, ship to address.
• Sales representative maps above provided information to SAP customer, material master data and proceeds with manual order creation in SAP system.
• Once order is saved, information related to availability, delivery date, order reference number and other parameters are sent back to EDI partner for confirmation.
• Similarly any change required in the order management is being handled via mail communication.
• Subsequent flow and information related to Delivery, invoice, and return process is also exchanged via mail.

Problem statement: This process has various drawbacks as below:

• Long processing cycle time due to human intervention and other dependencies involved.
• Error prone process.
• Highly inefficient and laborious due to manual effort involved.
• Cannot be tracked easily and lack of clear visibility in the process.
• Poor customer satisfaction due to delays and errors.
• Cost involved is high considering the manual work and human involvement at various steps.
• Involves redundant data entries and tasks

Approach adopted:

Usage of SAP Process Integration which is a platform to provide a single point of integration without changing existing complex network of legacy systems. It’s a powerful middleware by SAP to provide seamless end to end integration between SAP and non-SAP applications inside and outside the corporate boundary.

TO BE Business process:

Automate process of order creation: Orders will be initiated by EDI partner directly which would flow to SAP system (of agribusiness company) via IDOCS.

Interface: Net weaver Process Orchestration provides process integration and business rules management to help companies create system-to-system integration and seamless business processes.

Order responses: The order confirmation will happen in SAP depending upon the availability of material and order response will send the information to EDI partner via IDOC after validation

Delivery, invoice- Other information and documents related to order changes, delivery, invoice will be also exchanged via IDOCS.

Solution implemented:

1. Order creation/ change order: For order creation/change setup partner details in SAP using transaction WE20-

• Creation of new partner profile under partner type (KU) i.e. customer.
• It involves configuring of inbound parameters like Message type, process code and mapping it with function module as per business requirement.

Technical changes involved in include - LVEDAF2U using enhancement spot in program SAPLVEDA to populate values in inbound IDOC using below mapping

• Mapping order type with SAP order types, partner number mapped using EDPAR table in SAP, material mapping using EAN code from IDOC and other parameters mapping like sales division, order reason and delivery block etc.

By default, order is created with predefined delivery block since it needs to be validated by sales representative before confirming back to EDI business partner. New customized order reason can be used to distinguish a normal order from an EDI order.

2. Order response used for sending order confirmation, outbound parameters are maintained for EDI partner in transaction code WE20.

Prerequisites before configuration outbound parameters are:

• Output type with V1 application needs to be created with required access sequence and assigned to output procedure in NACE transaction.
• Port creation (receiver port) in WE21 transaction code which is used transferring data needs to be created and configured.
• Creation of new directory in AL11 transaction code where IDOC will be placed.

Outbound parameter setup require below steps:

• Configuring outbound parameters like Message type, Message code, output mode.
• Receiver port created above needs to be configured here.
• Standard or customized IDOC basic type and extension to be used.
• Application (V1) is mapped with output type, process code and corresponding function module.

Technical changes: Requirement routine created to trigger the output only when delivery block is removed by sales representative executive after order validation. This routine is configured in output procedure itself

3.Delivery and invoice related information is being sent to EDI partner, for that outbound delivery/invoice based parameters needs to be configured in outbound parameters.

• Message type, message code
• IDOC basic type and extension needs to be configured.
• Creation of new output types for V2 /V3 application for mapping it with process code and function module.
• Receiving ports and directory creation.

4.Notification updates: Customized report is created to  provide below information to sales service officers

• The list of the IDOCS (inbound/outbound) failed with the list of errors within this IDOC (unknown partner, unknown material, Division etc.).This enables them to take corrective actions.
• The list of the Sales orders successfully created – using this CS officers are able to confirm the sales order and release it for further processing.
• This program runs via batch job and sends output after every 15 minutes to key users/customer service officers.

Process and system Integration after implementation:

Automation and seamless integration of business processes achieved. Orders are triggered by EDI partner directly which would flow to SAP system (of agribusiness client) through IDOCS via SAP PI interface. Once confirmed and checked by sales representative executive, order response is being sent back to EDI business partner automatically. Delivery and invoice related information is also being sent to partner automatically using outbound IDOCS. 

Key challenges involved:

1. PI interface should be able to handle high volume due peak season to ensure stability and sustainability of the interface. 
2. Consistent and error free master data at the source. The goal is to avoid misaligned, erroneous data at the point of creation.
3. Complete and accurate customer, material master data mapping and maintenance in SAP is required.
4. To deliver the expected business result without any adverse impact on the system or any other existing order management process. This involves continuous program management between the business organizations.
5. Continuous monitoring of the interface after go-live to ensure seamless business process and system integration.
6. Failure Notifications and success updates should be sent instantly to end users without any delay so appropriate action can be taken up immediately.
7. Error handling process to reprocess failed updates and IDOCS to resolve issues.
8. User training and guidelines to be provided to adapt new ways of working and business process.

  Conclusion:

• Automation in order management,Delivery, invoice information exchange with third party EDI partner.
• Enhanced visibility and transparency in the overall process.
• Reduced overall cycle time with system and business process integration.
• Increasing efficiency of the business process and customer satisfaction with decreased overall lead
  time.

  Business Benefits:

1. Cost effective solution and process automation.
2. Enhanced business process with reduction in the processing time.
3. Reliable and better- delivery plans with correct scheduling arrangements due to automation.
4. Reduction in manual work and effort savings.
5. Customer satisfaction leading to repeat customer sales.
6. Increase in overall sales and cost optimization.

Recommendations:

• Post implementation it is required to maintain complete and error free master data, appropriate mapping is also required in production environment.
• Implementation of new Z program to provide list of the failed IDOCS with the list of errors (unknown partner, wrong material, missing data etc.).Report also provides list of sales orders which are successfully created via inbound IDOCS. Using SAP batch job, this information is provided to relevant business stakeholders and functional support team.
• Adequate training for the end key users to adapt new ways of working and business process.

Abbreviations

• EDI -Electronic Data Interchange.
• IDOC- Intermediate Document.
• ANSI X12 -American National Standards Institute.
• EDIFACT- Electronic Data Interchange for Administration, Commerce, and Transport.

The main objective of this document is to explain in detail the important function modules in SD Billing so that you can understand what happens inside each of them.

There are 3 main function modules in SD Billing and they are:

1. Function RV_INVOICE_CREATE
2. Function SD_COLLECTIVE_RUN_EXECUTE
3. Function RV_INVOICE_DOCUMENT_ADD

For more details on each one of these function modules please check the following documents:

1. Detailing Function RV_INVOICE_CREATE
2. Detailing Function SD_COLLECTIVE_RUN_EXECUTE
3. Detailing Function RV_INVOICE_DOCUMENT_ADD

Hopefully this will help you to find out where an issue is being originated!