cross-company sales order processing with allocation run

EHP3 for SAP ERP 6.0

March 2009

English

Cross-Company Sales Order Processing with Allocation Run (612)

SAP AGDietmar-Hopp-Allee 1669190 WalldorfGermany

Business Process Documentation

SAP Best Practices Cross-Company Sales Order Processing with Allocation Run (612): BPD

Copyright

© Copyright 2009 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, System i, System i5, System p, System p5, System x, System z, System z9, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, POWER5+, OpenPower and PowerPC are trademarks or registered trademarks of IBM Corporation.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.

SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.

These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

© SAP AG of 59


Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

External Process

Business Process Alternative/Decision Choice

Typographic Conventions

Type Style Description

Example text Words or characters that appear on the screen. These include field names, screen titles, pushbuttons as well as menu names, paths and options.

Cross-references to other documentation.

Example text Emphasized words or phrases in body text, titles of graphics and tables.

EXAMPLE TEXT Names of elements in the system. These include report names, program names, transaction codes, table names, and individual key words of a programming language, when surrounded by body text, for example, SELECT and INCLUDE.

Example text Screen output. This includes file and directory names and their paths, messages, source code, names of variables and parameters as well as names of installation, upgrade and database tools.

EXAMPLE TEXT Keys on the keyboard, for example, function keys (such as F2) or the ENTER key.

Example text Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation.

<Example text> Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries.

© SAP AG of 59


Contents

1 Purpose.................................................................................................................................. 5

2 Prerequisites........................................................................................................................... 6

2.1 Master Data and Organizational Data.............................................................................6

2.2 Business Conditions........................................................................................................7

2.3 Preliminary Steps............................................................................................................7

2.4 Posting Initial Stock.........................................................................................................7

2.5 Roles............................................................................................................................. 10

3 Process Overview Table.......................................................................................................11

4 Process Steps...................................................................................................................... 11

4.1 Creating Sales Order.....................................................................................................11

4.2 Allocation....................................................................................................................... 13

4.3 Delivery......................................................................................................................... 14

4.4 Billing............................................................................................................................. 16

4.5 Intercompany Billing......................................................................................................17

4.6 Checking EDI Transmission..........................................................................................19

4.7 Displaying Accounting Document in Company Code....................................................20

4.7.1 Displaying Details on the Inter-company Billing Document....................................20

5 Follow-up Processes............................................................................................................21

6 Appendix.............................................................................................................................. 22

6.1 Reversal of Process Steps............................................................................................22

6.2 SAP ERP Reports.........................................................................................................24

© SAP AG of 59


Cross-Company Sales Order Processing with Allocation Run

1 Purpose This documentation gives an overview of how this scenario is processed from a business point-of-view. This scenario demonstrates how an intercompany billing for cross company sales is carried out. Cross company sales is the standard tool to provide goods from plants belonging to a different company code than the selling entity belongs to.

In the scenario, the process flow follows the scheme:

The sales order of the respective type YFSO is entered in Sales organization 1000, which belongs to company code 1000. This company code does not have an own stock in an own plant for the respective material, therefore the delivery requirement is passed to plant 1010 (setting in the sales view of the material; Sales organization 1000, distribution channel 20, division 10; delivering plant 1010).

This plant belongs to company code 1010. The warehouse of this plant carries out the necessary logistics execution as defined in the warehouse scenarios. After goods issue, the billing to the end customer can be carried out in sales organization 1000 analog to the normal customer billing without intercompany features.

After billing the end customer from sales organization 1000, the intercompany billing (ICB) can be done from company code 1010 (Sales organization 1010, Distribution channel 30) to company code 1000. This will involve billing type ZIV created through billing due list (VF04). The ICB will be booked to FI and CO as normal customer invoice. It will contain Sales organization 1000 as the customer 491000 (BP, PY).

The ICB then will be transmitted from company code 1010 to company code 1000 via EDI. In the inbound IDOC processing, company code 1000 will receive an incoming invoice from the vendor 493000. The invoice will be booked to FI and CO as a normal vendor invoice without PO reference.

2 Prerequisites

2.1 Master Data and Organizational DataDefault Values

Essential master and organizational data was created in your ERP system in the implementation phase, such as the data that reflects the organizational structure of your company and master data that suits its operational focus, for example, master data for materials, vendors, and customers.

The business process is enabled with this organization-specific master data, examples are provided in the next section.

Operational Focus

© SAP AG of 59


SAP Best Practices delivers standard values for more than one operational focus area, such as Services, Trade or Manufacturing. This means that you may find more than one master data table below. Use the master data that matches the operational focus of your company (Service, Manufacturing, or Trading).

Additional Default Values

You can test the scenario with other SAP Best Practices default values that have the same characteristics.

Check your SAP ECC system to find out which other material master data exists.

Using Your Own Master Data

You can also use customized values for any material or organizational data for which you have created master data. For more information on how to create master data, see the Master Data Procedures documentation.

Use the following master data in the process steps described in this document:

Master / org. data Value Master / org. data details Comments

Company Code 1000 Company Code 1000

Company Code 1010 Company Code 1010

Plant 1010 Distribution Center

Storage Location 1040 Shipping w/o LWM

Sales Organization 1000 Dom. Sales Org

Distribution Channel 20 Wholesale

Division 10 Product Division 10

Sales organization 1010 Int. Sales Org

Distribution channel 30 Other Sales

Division 10 Product Division 10

Material 1 AFS-H1103TShirt_2

with delivering plant 1010 for Sales organization 1000

Customer AFSC001Customer IN1

AFSC001 in Sales Area 1000/20/10

Customer Intercompany

491000

Customer Company 01

491000 in Sales Area 1010/30/10

Vendor 493000 NATIONAL_PROD_PLANT_VENDOR

493000 in Purchasing Organization 1000

© SAP AG of 59


2.2 Business ConditionsThe business process described in this Business Process Documentation (BPD) is part of a bigger chain of integrated business processes or scenarios. As a result, you must have completed the following processes and fulfilled the following business conditions before you can start any activities in this scenario:

Business condition Scenario

To run through this scenario, some prerequisite processes steps have to be done.

To Execute this activity, run the Business Process Procedure for Prereq. Process Steps (BB - 154) scenario.

The following steps are required:

Roll MM Period to Current Period

Prereq. Process Steps (BB - 154)

© SAP AG of 59


2.3 Preliminary StepsThis section contains activities that you need to carry out before you run through the Business Process Documentation. Usually, you only have to execute these steps before you run the BPD for the first time, for example to create initial stock for goods movements.

2.4 Posting Initial Stock

UseThe purpose of this activity is to create initial stock of the material. Once you have created the initial stock, you will have sample stock available to run the BPD several times. Once the stocks have been used up, execute this activity again to create more.

Procedure

1. Access the transaction choosing one of the following navigation options:

Option 1: SAP Graphical User Interface (SAP GUI)

SAP ECC menu Logistics Materials Management Inventory Management Goods Movement Goods Movement (MIGO)

Transaction code MIGO

© SAP AG of 59


Option 2: SAP NetWeaver Business Client (SAP NWBC) via business role

Business role Warehouse Clerk

(SAP_BPR_WAREHOUSESPECIALIST-S)

Business role menu Warehouse Management Receiving Other Goods Movement

© SAP AG of 59


2. Make the following entries on the MIGO overview screen:

3. If necessary choose Hide Overview (Shift+F9) and Close Detail Data in the lower half of the screen to get the full screen.

Field name Description User action and values Comment

Business Transaction

A01 – Goods Receipt

Select A01 – Goods Receipt from the 1st Dropdown Menu

Business Transaction

R10 – Other Select R10 – Other from the 2nd Dropdown Menu

Movement Type 501 Receipt w/o purchase order into unrestricted-use stock.

© SAP AG of 59


4. Choose Enter.

5. Enter the material number in the Material short text field and choose Enter. Instead of the material number the Material short text will appear.


Material ShortText

AFS-H1103 Line 1: T-Shirt 2

© SAP AG of 59


6. If necessary choose Open Detail Data in the lower half of the screen.

7. Choose Quantity tab page, enter the quantity, and the unit of measure then choose Enter:


Qty in UnE 80

EUn NOS

© SAP AG of 59


8. Choose Where tab page, enter plant and storage location as follows, then choose Enter:


Plant 1010

Stor.Loc 1040 Shipping - (w/o Lean WM).

© SAP AG of 59


9. Choose Batch tab page, select the Grid Value by using the match code (F4). Select the appropriate line from the first column Base values and make double-click.


Grid Value S WHT Grid Value for sizes and colors.

© SAP AG of 59


10. Choose Enter again and choose Close Detail Data in the lower half of the screen to get the full screen.

11. Repeat these steps for the next lines. After every line choose Enter.

Material ShortText

Qty

in UnE

EUn Plant Stor.Loc Grid Value

(Sizes and Colors)

Stock

Category

Comment

AFS-H1103

80 NOS 1010 1040 M WHT Line 2

AFS-H1103

100 NOS 1010 1040 S BLK Line 3

AFS-H1103

100 NOS 1010 1040 M BLK Line 4

AFS-H1103

80 NOS 1010 1040 L WHT Line 5

AFS-H1103

100 NOS 1010 1040 L BLK Line 6

© SAP AG of 59


12. Choose Save. The following message will appear: Material document XXX posted.

13. Choose Back (F3) to go back to the SAP Easy Access screen (SAP GUI) or choose Exit (Shift+F3) and confirm the Business client message with Yes to return to SAP Home (SAP NetWeaver Business Client).

ResultYou have created initial stock.

You can check the stock by using the transaction: /n/afs/md04. On the AFS Stock/Requirements List: Initial Screen, enter the material number in the Material field and enter the plant 1010 (or select from the list) in the appropriate field. Choose Enter. On the AFS Stock/Requirements List screen, you have different views concerning stock and requirements.

Procedure



SAP ECC menu Logistics AFS Central Functions AFS Material Requirements Planning AFS Evaluation AFS Stock/Reqs list

Transaction code /n/afs/md04

© SAP AG of 59



Business role Production Planner (AFS) (SAP_BPR_PRODUCTIONPL_AFS-S)

Business role menu Production Planning MRP AFS Stock/Requirements List

© SAP AG of 59


2. On the AFS Stock/Requirements List: Initial Screen, enter the material number and the plant or select with F4. Then choose Enter.


Material AFS-H1103

Plant 1010

© SAP AG of 59


3. On the AFS Stock/Requirements List screen, the stock is assigned by:

Status Description

A - Free available stock

I - Additional information

© SAP AG of 59


4. The Stock number mirrors the batch number. On the view Additional information, you will also see the Requirements.

5. Choose Back (F3) to the AFS Stock/Requirements List: Initial Screen and change the material number to AFS-H1103.

6. Choose Enter to review the stock for material AFS-H1103.


2.5 Roles

UseThe following roles must have already been installed to test this scenario in the SAP Netweaver Business Client (NWBC). The roles in this Business Process Procedure must be assigned to the user or users testing this scenario. You only need these roles if you are using the NWBC interface. You do not need these roles if you are using the standard SAP GUI.

PrerequisitesThe business roles have been assigned to the user who is testing this scenario:

Business role Technical name Process step

Production Planner (AFS)

SAP_BPR_PRODUCTIONPL_AFS-S Display Stock/Requirements List

Sales Administration

SAP_BPR_SALESPERSON-S Create Third-Party Sales Order, Change Order Quantity

Sales Billing SAP_BPR_SALESPERSON-S2 Billing Accounts Receivable

Warehouse Clerk SAP_BPR_WAREHOUSESPECIALIST-S

Delivery and Post Goods Issue

Employee (Professional User)

SAP_BPR_EMPLOYEE-S Assignment of this role is only necessary if you want to print the invoice via the system icon Print Invoice. Automatic printing is possible without assignment of this role.

Sales Administration (AFS)

SAP_BPR_SALESPERSON_AFS-S Allocation run

General Ledger Accountant

SAP_BPR_FINACC-S Displaying Details on the Inter company Billing

© SAP AG of 59


3 Process Overview Table

Process step External process reference

Business condition

Business role

Trans-action code

Expected results

Post Goods Receipt

Warehouse Clerk

MIGO Goods receipt is posted

Create Sales Order


VA01 Sales order has been created.

Order Confirmation


VA02 Print order confirmation

Allocation Run Sales Administration

J3AT Allocated the stock to the requirements.

Delivery and Post Goods Issue

Warehouse Clerk

VL01N Goods is delivered and posted

Billing Sales Billing VF01 Billing is created

Incoming Payment

Accounts Receivable (157)

Accounts Receivable

See scenario no. 157

See scenario no. 157

Closing Operations

Sales: Period End Closing Operations (203)

© SAP AG of 59


4 Process Steps

4.1 Creating Sales Order

UseThe sales order is created in company code 1000, sales organization 1000.

Procedure



SAP ECC menu Logistics Sales and Distribution Sales Order Create

Transaction code VA01

© SAP AG of 59



Business role Sales Administration (SAP_BPR_SALESPERSON-S)

Business role menu Sales Sales Orders Create Sales Order

© SAP AG of 59


2. On the Create Sales Order: Initial Screen, make the following entries or select from the match code (F4), then choose Enter:


Order Type YFSO Order Type for Sales Order.

Sales Organization

1000

Distribution Channel

20

Division 10

© SAP AG of 59


3. On the Create Sales Order: Overview header screen, enter the following data for sales order # 1, then choose Enter:


Sold-to pt AFSC001 Enter here customer.

Pur. Order <Free text entry> Enter a PO number or a text.

© SAP AG of 59


4. Choose the AFS Item overview tab page and enter material in the Material field.


Material AFS-H1103

RqDlv.date <System Date> The requested delivery date for a particular line can be maintained individually, by default it will be copied over from the header.

© SAP AG of 59


5. Choose Enter.

6. For entering the order quantity, choose Matrix entry.

7. The new screen Sales/Distribution will display the grid of the material. Maintain here the desired quantities, then choose Enter and choose Back (F3):

Dim.values XS S M L XL XXL XXXL

∑

BLK 10

WHT

BLU

GRE

RED

YLW

PNK

BRW

ROY

© SAP AG of 59


8. Choose Enter.

9. Choose Back (F3).

10. Choose Save (Ctrl+S). In the case you have not maintained all mandatory fields, for example, a PO number you will receive a message Document Incomplete. If you do not want to complete, choose Save. If you want to complete, choose Edit. A list will appear with all data still needs to be completed. Double-click the item. Enter the missing data and choose Edit next data (F5). As soon as all fields are maintained you will receive a message Document is complete. Choose Save (Ctrl+S).

11. You receive a message Sales Order XXX has been saved.

12. Record the sales order number.


Result A sales order was created that needs to be delivered from plant 1010.

4.2 Allocation

UseThe A – Run will allocate the requirements and stocks according to the FIFO logic (first in – first out) and defined fulfillment rate (header: 80% & item 60%). The A-Run will put the status “F” (fixed) if the fulfillment rate is fulfilled. The allocation of goods is necessary to create a delivery note. In case of the cross company sales, the allocation takes place in plant 1010, because there are no stocks and logistics data for the material AFS-H1103 in plant 1000.

Procedure1. Access the transaction choosing one of the following navigation options:


SAP ECC menu Logistics Sales and Distribution Allocation Run Online Processing

Transaction code J3AT

© SAP AG of 59



Business role Sales Administration (AFS) (SAP_BPR_SALESPERSON_AFS-S)

Business role menu Sales Allocation Run AFS Allocation run

© SAP AG of 59


2. On the Arun flow screen, make the following entries or select from the list:

Field name User action and values Comment

Allocation Type YF01 Standard H80E I60W AFS BP

Mode 1 Normal

Release check COMPLETE releasechecks

Allocation List Set Flag

© SAP AG of 59


3. Choose Execute (F8).

4. On the Arun Selection Order Items by Material, view Material screen, insert Plant 1010 (or select from the list) and insert material AFS-H1103.

5. Choose Enter.

6. Go to view Sales 1 and check if the following entries are made:


Open to delivery <Enter system date> From <current date> To <current date + 12 month>

Sales Organization 1000

Distribtion Channel 20

Division 10

Sales Document Type YFSO

© SAP AG of 59


7. Choose Execute(F8).

8. On the Arun Selection List screen, mark all lines if not already done and then choose Execute (F8).

9. You receive the Arun Result List. You will recieve the ARun Result List. Status F (fixed) means the fulfillment rate is fulfilled. Sales order is open to delivery (green). Sales order with status R (reserved) cannot be delivered (red). Save the ARun Result List.


ResultYou have allocated the necessary stock from company code 1010 to the sales order in company code 1000.

4.3 Delivery

UseThe delivery is created sales-order-related in plant 1010, shipping point 1010. In the same transaction, the quantity of the material can be picked manually. The material is not warehouse managed; therefore no WM-transport request is necessary. During the creation of the delivery the goods issue can be posted manually as well.

Procedure



SAP ECC menu Logistics Sales and Distribution Shipping and Transportation Outbound Delivery Create Single Document With Reference to Sales Order (VL01N)

Transaction code VL01N

© SAP AG of 59



Business role Warehouse Clerk (SAP_BPR_WAREHOUSESPECIALIST-S)

Business role menu Warehouse Management Shipping Create Outbound Dlv. w/o Ref.

© SAP AG of 59


2. If you are in SAP NetWeaver Business Client, on the Create Outbound Delivery without Order Reference screen, choose With Order Reference.

3. On the Create Outbound Delivery with Order Reference screen, make the following entries or select from the list:


Shipping point 1010

Selection date <Enter system date> Make sure that the date was confirmed by the ATP check! Otherwise enter a future date. The date with which you select the delivery that you want to process.

Order <Enter here the sales order number>

Only the Sales orders with status “F” can be delivered.

© SAP AG of 59


4. Choose Enter. Fields on the Delivery Create: Overview, view Item Overview screen are already populated. In the field delivery quantity you will see 10.

5. Go to view AFS Data, then AFS Picking.

6. In the Pick quantity field, enter the value from the Delivery quantity field.

7. Choose Enter.

8. Choose Post goods issue. You will receive a message Delivery XXX has been saved.

9. Record the document number.


ResultThe delivery document in plant 1010 has been created. Then the picking and goods issue processing was carried out. Now the transaction is due for billing.

You may check the accounting document for the goods issue by this way:



SAP ECC menu Logistics Sales and Distribution Sales Order Display

Transaction code VA03

2. On the Display Sales Order: Initial Screen, enter the order number

3. Choose Display Document Flow.

4. Mark GD. Goods issue: delvy 49xxxxxxxx, choose Display document.

5. Choose Accounting Document. Double-click the accounting document number; you will see the accounting document result.



Business role Sales Administration (SAP_BPR_SALESPERSON-S)

Business role menu Sales Sales Orders

2. Choose the tab page of All Sales Orders (refresh the current query if necessary).

3. Mark your sales order and choose Display.

4. From the menu, choose More… Environment Document Flow

5. Mark GD. Goods issue: delvy 49xxxxxxxx, choose Display document.

6. Choose Accounting Document. Double-click the accounting document number; you will see the accounting document result.

Material Posting Key

Account Description Amount Cost Element / CO Object

Trading Goods

99 22111100 Stk TG 11,000.00-

81 40111100 PL-Vnd- Mtl 11,000.00

© SAP AG of 59


4.4 Billing

UseVia transaction VF01 the invoice to the end customer is created and posted to accounting in company code 1000.

Procedure



SAP ECC menu Logistics Sales and distribution Billing Billing document Create

Transaction code VF01

© SAP AG of 59



Business role Sales Billing

(SAP_BPR_SALESPERSON-S2)

Business role menu Sales Billing Create Billing Document

© SAP AG of 59


2. On the Create Billing document screen, enter the delivery number from the previous step.

3. Choose Enter.

4. On the Create Invoice Overview SKUs screen, view AFS Item Overview, AFS Pricing and Billing Items, make sure that all your required data are already populated in the fields. The quantity must be the same as the one allocated in the Arun.

5. Choose Save. The system displays the message Document 9xxxxxxx saved.

6. Note your invoice number.


ResultThe end customer invoice has been created and been posted to the accounting in company code 1000. The second result is that the intercompany billing for the transaction in 1010 becomes due for processing.

You may check the accounting document by this way:



SAP ECC menu Logistics Sales and distribution Billing Billing document Display


© SAP AG of 59


2. Enter the Billing document.


4. Mark Accounting document 9xxxxxxx, choose Display document.



Business role Sales Billing (SAP_BPR_SALESPERSON-S2)

Business role menu Sales Billing

© SAP AG of 59


2. Choose Change Billing Document.

5. Enter the Billing document.


7. Mark Accounting document 9xxxxxxx, choose Display document.



Trading Goods

01 AFSC001 Customer IN 1 7,748.00

50 31111100 Sal-Dom-Dir-TG 7,450.00-

50 16622121 CST pybl-BP 21 298.00-

© SAP AG of 59


4.5 Intercompany Billing

UseVia transaction VF04 the intercompany invoice can be created and the EDI message is sent from one company code to the other automatically.

Procedure



SAP ECC menu Logistics Sales and Distribution Billing Billing Document Process Billing Due List


© SAP AG of 59


2. If you are in SAP NetWeaver Business Client, choose More Billing Document Billing due list (Ctrl+F12)

3. On the Maintain Billing Due list screen, make the following entries:


Billing Type IV

Billing Date to <Enter system Date>

Sales Organization 1010

Delivery-related <deselect>

Intercompany Billing <select>

© SAP AG of 59


4. Choose DisplayBillList (F8)

5. You will receive the billing due list for Intercompany billings in sales organization1010.

6. Deselect all lines.

7. Select the line with your invoice number.

8. Choose Individual billing document (Shift+F6).

9. On the Create Intercompany Billing Overview SKUs screen, AFS Item overview tab page, make sure that all your required data are already populated in the fields. The quantity must be the same as the one in the end customer invoice.

10. Choose (More ) Goto Header Output from the menu bar and check the automatic output determination. You will find 2 records:

Status Output Description Medium

Partner Function

Partner Language

Yellow RD00 Invoice Print output

BP 491000 EN

Yellow RD04 Invoice Receipt MM

EDI BP 491000 EN

© SAP AG of 59


11. Choose Save.

12. You will receive a message Document XXX has been saved.




Trading Goods

01 491000 Customer Company 01

6,187.50

50 31111100 Sal-Dom-Dir-TG 5,500.00-

50 16622111 VAT pybl-BP 21 687.50-

© SAP AG of 59


4.6 Checking EDI Transmission

UseYou can check and demonstrate the automatic posting of a vendor invoice to company code 1000.



SAP ECC menu Logistics Sales and Distribution Foreign Trade/Customs Communication / Printing Communication / Printing Communication Display IDoc

Transaction code WE02

© SAP AG of 59



Business role Sales Administration (AFS) (SAP_BPR_SALESPERSON_AFS-S)

Business role menu Sales Foreign Trade/Customs Display IDoc

© SAP AG of 59


2. On the IDOC List screen, make the following entries:


Created on <Enter system Date>

Partner number <3-digit System ID>CLNT<Client number>

For example, KADCLNT105

© SAP AG of 59


3. Choose Execute (F8)

4. You will find your IDOC in the results list on both, the outbound and inbound side. In case there are many IDOCs displayed, you can find your IDOC by:

Field name Values Comment

Partner LS/ /<3-digit System ID>CLNT<Client number>

For example, LS//KADCLNT105

Basic Type INVOIC02

Date <System date>

Time <The last minutes>

Direction Inbox

© SAP AG of 59


5. Double-click the IDOC number.

6. Expand the segments tree and check the content of the segments.

7. Expand the status report tree and check for status 53 Document 19<8-digit document number> 1000<Fiscal Year> was posted.

8. Note the 19XXXXXXXX number.


ResultThe IDOC transmission has been shown.

4.7 Displaying Accounting Document in Company Code

UseIn the sales organization 1000, company code 1000, an automatic posting to the vendor account is performed in financial accounting for inter-company billing.

4.7.1 Displaying Details on the Inter-company Billing Document



SAP ECC menu Accounting Financial Accounting General Ledger Document Display

Transaction code FB03

© SAP AG of 59



Business role SAP_BPR_FINACC-S (General Ledger Accountant)

Business role menu General Ledger G/L Account Processing Display Document

2. On the Display Document: Initial Screen, check the following field:


Document number

19XXXXXXXX (Number of your intercompany accounting document)

To find out the accounting document number use transaction VF03, enter the document number of the inter company billing and choose Accounting.

Company code 1000

Fiscal year <Fiscal Year>

3. Confirm your entries.

4. The system displays the document items on the Document overview screen.


Result

The accounting document list as below:

CoCd Posting Key


1000 40 40500000 Cogs intercomp AFS

6,187.50

31 493000 NATIONAL_PROD_PLANT_VENDOR

6,187.50-

© SAP AG of 59


5 Follow-up Processes

You have finished all activities that are part of the business process described in this document.

To accomplish subsequent activities of this business process, carry out the process steps described in one or more of the following scenarios, using the master data from this document.

Accounts Receivable (157)

UseIn this activity you post the incoming payment.

ProcedureComplete all activities described in the Business Process Documentation of the scenario: Accounts Receivable (157) (Chapters “Post Payments using Automatic Payments Program”, “Post Incoming Payment from Customer Manually”, “Automatic Clearing of open items in customer accounts”, “Manual Clearing of Open items in customer accounts”) using the master data from this document.

Sales: Period End Closing Operations (203) (optional)

Use

This scenario describes the collection of periodic activities such as day ending activities or legal requirements like Intrastat and extrastat reporting.

ProcedureComplete all activities described in the Business Process Documentation of the scenario: Sales: Period End Closing Operations (203) (Chapters “Review Sales Documents blocked for billing”, “Review Billing Due List”, “Review Log of collective invoice creation” and “Review List Blocked (for accounting) Billing Documents”) using the master data from this document.

6 Appendix

6.1 Reversal of Process StepsIn the following section, you can find the most common reversal steps, which you can take to reverse some of the activities described in this document.

Sales Order Entry

Transaction code (SAP GUI) VA01

Reversal: Delete Sales Document

Transaction code (SAP GUI) VA02

Business role Sales Administration

© SAP AG of 59


Business role menu Sales Sales Orders

Choose All Sales Orders tab page.

Mark your sales order and choose Change.

Comment Choose the menu Sales Document Delete

© SAP AG of 59


Allocation Run

Transaction code (SAP GUI) J3AT

Reversal: Cancel allocation run

Transaction code (SAP GUI) /AFS/ARRG

Business role SAP_BPR_SALESPERSON_AFS-S

Business role menu Sales -- Allocation Run --ARun Reorganization

Comment Choose Deallocation and choose Execute.

© SAP AG of 59


Delivery Process

Transaction code (SAP GUI) VL01N

Reversal: Delete Delivery



Business role menu Warehouse management Shipping

Choose All Deliveries tab page.

Mark your delivery and choose Change.

Comment Choose the menu Outbound Delivery Delete

© SAP AG of 59


Check Batches


Reversal: Edit Batch Number



Business role menu Warehouse management Shipping Display Outbound Delivery

Comment

© SAP AG of 59


Picking

Transaction code (SAP GUI) VL06O

Reversal: Remove Picking Quantity from Delivery Item






Comment

Post Goods Issue


Reversal: Reverse Goods Issue.

Transaction code (SAP GUI) VL09


Business role menu Warehouse management Shipping Cancel Goods Issue for Delivery Note

Comment

© SAP AG of 59


Billing

Transaction code (SAP GUI) VF04

Reversal: Cancel Billing document

Transaction code (SAP GUI) VF11


Business role menu Sales Billing Change Billing Document

Comment Go to transaction VF11, enter the relevant billing document number, choose Enter, and save your result. An invoice cancellation document has been created balancing the original invoice.

6.2 SAP ERP Reports

UseThe table below lists the reports that you can use to obtain additional information on this business process.

You can find detailed descriptions of the individual reports in the following BPD documents, which provide a comprehensive compilation of all important reports:

Financial Accounting: SAP ERP Reports for Accounting (221)

Logistics Processes: SAP ERP Reports for Logistics (222)

Note that the descriptions of some reports that are an indispensable part of the process flow may be located directly in the section where they belong.

ReportsReport title Transaction

code ( SAP GUI)Comment

List of Sales Orders VA05 A list of all selected sales orders is displayed.

List Billing Documents VF05 A list of all selected billing documents is displayed.

Orders within Time Period SD01 A list of sales orders within a specific time period

Incomplete SD Documents

V.02 A list of all incomplete documents on the basis of the specified selection criteria is displayed.

Outbound delivery monitor VL06O Monitor for collective processing of deliveries and for obtaining information on general shipping processing.

© SAP AG of 59