1201 / Cross Company Sales Configuration

Monday, May 19, 200310:10 AM - 11:10 AMContent Area: Order

Management

Dave Hubert Molex

Business Process Requirement

• Molex is a global implementation of SAP . Single shared instance used by sales org companies in 18 countries and 45 manufacturing/distribution centers.

• Customers want to order upon their local or regional sales org and receive shipments from any manufacturing plant eliminating buy-stock-resell.

Process Example

• Customer places order to the North American sales organization.

• ATP requirement for delivery directly from a plant in Japan.

• North American company bills the end customer.

• Japan company bills the North American company and cost of sales , a/r , a/p , COPA and SIS/BW all reconcile.

Demonstration

• R/3 system used is 46c support pack 40 in April , 2003.

WRF File

Configuration Steps

• MM & SD master data• SD Billing and Pricing • PA Flow of Values• SIS/BW updating• FI AR/AP EDI• FI G/L master data and PCA rule• EDI partners• Process Trace Verification

Define Account Groups for Internal Vendors and Customers With External Numbers

• For configuration in a development system , the customer and vendor number must match that of the production system.

• Use a consistent convention so that the same entity as a customer and vendor is easily recognized by the code. (I.E. V-xxxx or c-xxxx).

Account Group Number Ranges

• Object ‘Debitor’ for customer. Use transaction XDN1 to create and assign a number range for an account group. OBD2 to create the customer account group.

• Object ‘Kreditor’ for vendor. Use OSMJ to define the range. XKN1 to create number range. OBAS to assign to the account group. OMSG to create the account group.

Create the Customer and Vendor Masters in Development , QA and Production

• Do not define your vendors as plants so as to trigger stock transport order purchasing.

• Create all customers and vendors for all sales orgs and purchasing orgs with necessary company code views. XD01 for customer and XK01 for vendor.

• Indicate the customer number of the vendor in the vendor master and the vendor number in the customer master in change mode.

Vendor Customer Association

Define Intercompany Billing

• Define the sales area that represents the delivery plant – OVV9

• Define the customer that represents the sales organization of the order. (The sales org of the end customer order which will be the customer of the sales org of the delivery plant) – OVVA. Please note that because this uses an actual customer number , to do the maintenance in a development system with transport suggests the use of an external number for the account group and an intelligent convention.

Typical Entries for Sales Org Customers

Create a Special Billing Type for Intercompany Billing

• VOFA. You may want a separate type for cross company sales intercompany billing versus the intercompany billing of a stock transport order. This to derive different copy controls , SIS or BW update rules and especially the pricing procedure.

• Assign this type to the end customer order type – OVV8. Define copy control VBX2.

• Define background user authorization for this billing type plus global invoice entry!

Define Pricing Procedure for Intercompany Billing

• Likely to be the similar to the end customer procedure with special intercompany conditions. SAP provides material specific price and percent condition. Some sites may always compensate as a percent of end customer revenue and some may have fixed price relationships. Only a condition type defined as intercompany will be calculated in an intercompany billing.

Simple Pricing Procedure

Billing Document Example

Copy Control Using Origin Price If Desired

Intercompany Pricing Conditions

• One entry for 2 separate conditions. First condition defined as the cost to the sales organization of the order. The second condition defined as the price from the sales org of the delivery plant.

• This facilitates the map to PA and the postings to SIS.

Master Material Specific Condition

Condition for Inter-co Cost

Maintain the Intercompany Conditions – VK11

• No SAP authorization based upon sales org of order. No validation of material with sales org of order as a key. Only conditions using sales org perform these functions so access to the pi01, pi02 conditions requires procedural enforcement.

• Maintain the master condition and the reference condition will find the value.

PA Postings

• Flow of value conditions in SD pricing of the billing document to Profitability Analysis determines whether a cost or revenue account is defined.

• This is why there are separate pricing conditions in the end customer billing document as a cost to the selling org and as a revenue condition in the billing document of the delivery org. Both derived from a common condition.

Flow of Actual Values KE4I

SIS/BW Postings in End Custoemr Pricing

SIS Update Rule Interco

SIS Update Rule Standard

IMG – Inter-company Billing

Define Intercompany Invoice Processing

• WEL1 – define the edi logical address.String entry with intelligence. The

first 4 positions are the characters of the company of the delivery plant. The rest of the entry is the customer number of the sales org of the order. Remember that company is a character field not a numeric field although numbers may be in the entry.

WEL1 Entry

Matching Companies to Vendor and Customer for Automated EDI Invoice

Define Output Type – V/40

• Defined so as to create an idoc for internal edi posting upon billing document save.

• SAP has provided RD04 keyed by the sales org of the intercompany invoice (sales org of the delivery plant) and the customer bill to partner (customer representing the sales org of the order to the end customer).

Output Type Settings

Output Type Settings

Maintain Output Determination

Maintain Output Procedure for Billing – V/42

Assign Output Procedure to Billing Type – V/25

Create Output Condition Records – VV31

FI Configuration for Incoming Invoice -OBCE, OBCC, OBCD,OBCB

Posting Keys for Incoming Invoice by Vendor Per Company - OBCE

OBCE Considerations

• Input tax field entry must be valid for this company.

• Standard unit of measure for common parts must default.

• Review by table t076s using se16.

GL Accounts - OBCB

• Best to review by se16 for table t076i to audit the entries.

• Define a ‘cost of goods sold’ account for the posting of the incoming invoice derived from a sale to the end customer.

• Enter partner type LI , vendor account number , company code , * in goods and services.

• Enter g/l account and company code.

OBCB Example

Additional Accounts for EDI - OBCC

• Enter partner type LI.• Enter vendor number.• Enter company code.• Enter * for acct assignment id.• Review in table t076k.

OBCC Example

Tax Code Rates by Vendor and Arrival Country - OBCD

• Country is the country of the company of the sales org of the end customer order. The company receiving the intercompany invoice.

• Enter partner type LI , vendor account , tax type ‘vat’ , rate , country and tax code.

• Review in table T076M.

OBCD Example

Define the G/L Accounts and Reconciliation Accounts for Tax and Field Display – FSS2

• In tax category by account set * for tax category.

• Mark posting without tax allowed.• Make sure that the field status group

allows entry of the quantity and unit of measure fields. If not you may see some unusual messages saying that the fields are not in specific screens.

• One account is defined in OBCB , the other in the vendor master.

Reconciliation Account for Vendor

G/L Account Master Data

Substitution for Profit Center Accounting

• If you do not want the profit center of the delivery plant to pass into the incoming mm invoice , an FI substitution rule can be used to default a relevant profit center for the company of the sales org of the order.

• Transaction OBBH substitution by company code. Prerequisite step:Document type = ‘**' AND G/L account = ‘******‘ as defined obce and obcb.

Substitution Example

Maintain the EDI Partner Profiles – WE20

• Vendor and Customer Partners must be maintained for special processing of message type ‘invoic’.

• If using a 46c release or later , do not follow standard SAP advice to use message code ‘FI’ as that is no longer usable with Logistics Invoice Verification.

Vendor Example

Vendor Example

Message code is blank with LIV

Vendor Example

Agent for workflow review of idoc failure is at the company of the outbound SD intercompany billing document

Customer Example

Customer Example

Generic Port defined for edi or ale

Customer Example

Customer Example

Customer Example

• The other tabs for customer are irrelevant• Post processor , edi standards , telephony.• Process code sd08 and necessary function

module is provided by SAP.

Process Tracking

• Create the sales order process and post the normal customer invoice by the sales org of the order and then the intercompany invoice by the sales org of the delivery plant.

Process Tracking

• Check the accounting document for the posting of the intercompany invoice.

Process Tracking

• Note the header of the accounting document an the user.

Process Tracking

• Go to the header output of the SD intercompany billing document.

• For the rd04 output type (or equivalent) , use the ‘processing log’ pushbutton.

• If the output type is shown with a green light , an idoc should have been created. Write down the idoc number.

Process Tracking

Process Tracking

• Go to WE05 to review the specific idoc. • Enter the idoc on the additional tab manually

(does not cut and paste)• Check the green or red status codes

Process Tracking

• Double click on the message type ‘invoic’ to expand to detail .

• Expand the status records code 53 for a green light or 51 for a red light. If green , there should be a message listing an accounting document.

Process Tracking

• Use fb03 to display the accounting document as an incoming invoice to the company of the sales org of the order.

Process Tracking

• Note the header of the accounting document and the user.

Reference Materials

• Service.sap.com white paper ‘Customizing Value Chain 9’ by Best Practices for mySAP Automotive.

• OSS notes 31126,137686,162990,308989• SAP release notes for 3.0A Intermediate

document structure ‘invoic01’.• SAP IMG help ‘Automatic posting to Vendor

Account (SAP-EDI)• Trial and Error.

Thank You for Attending!

Please Remember to Complete and Return Your Evaluation Form

Following This Session.

Session Code: [1201]