EHP5 for SAP ERP 6.

0 June 2011 English

Sales: Period End Closing Operations (203)
Business Process Documentation

SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf Germany

SAP Best Practices

Sales: Period End Closing Operations (203): BPD

Copyright
© 2011 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, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation. Linux is the registered trademark of Linus Torvalds in the U.S. and other countries. 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, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, StreamWork, 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 other countries. Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd. Business Objects is an SAP company. Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase, Inc. Sybase is an SAP company. 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

Page 2 of 33

SAP Best Practices

Sales: Period End Closing Operations (203): BPD

Icons
Icon Meaning Caution Example Note Recommendation Syntax External Process Business Process Alternative/Decision Choice

Typographic Conventions
Type Style Example text Description 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 EXAMPLE TEXT Emphasized words or phrases in body text, titles of graphics and tables. 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. 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. Keys on the keyboard, for example, function keys (such as F2) or the ENTER key. Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation. Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries.

Example text

EXAMPLE TEXT

Example text <Example text>

© SAP AG

Page 3 of 33

............................................................................................17 4...................11 Reviewing List Blocked (for Accounting) Billing Documents ......8 4 Process Steps............7 Reviewing Outbound Deliveries for Goods Issue...................................................................1....21 4...........................................6 2...................................................................................................................................................................1............................5 2 Prerequisites...........1....................29 4...............................1 Master Data and Organizational Data...1.................................1..........................................................................................................................................5 2...............................32 5......24 4.........................3 Extract Registers...........................................................2 Business Conditions.............SAP Best Practices Sales: Period End Closing Operations (203): BPD Contents 1 Purpose........................8 Reviewing Sales Documents Blocked for Billing......4 Monthly Utilization......................2.31 5 Appendix...30 4.................13 Settling the Sales Order to Profitability Analysis (Service Provider).................................................................................19 4.......................1 Update for Initial Stock Upload .....................1............................................................27 4....................................................................................1..................1.......4 Reviewing Sales Orders Due for Delivery ................12 4..................................2 Reviewing Incomplete Sales Orders....................10 4......................................18 4............................10 Reviewing Log of Collective Invoice Creation ......5 Reviewing Log of Collective Delivery Creation........................................20 4...................................................................................................................................1 Closing Operations.........10 4.................2........1 Reviewing Blocked Sales Orders.............................................................13 4..............................5 2.......22 4.............2 Update Registers............................................3 Reviewing Sales Documents Blocked for Delivery..........6 Reviewing Incomplete SD Documents (Deliveries)..............1 Reversal of Process Steps.............26 4.....3 Update for Outgoing Entry............................................................................................1.......................................................25 4....16 4............................12 Calculation of Work in Process (Service Provider)....5 Generating ER 1 Report.................................................................................................................................................................................10 4..................................2 Update for Stock Uploading from Production.........1....1.......................................................................25 4.....2.......................................1................15 4..........32 © SAP AG Page 4 of 33 .......................................1..................................................................................................................................................9 Reviewing Billing Due List.........7 3 Process Overview Table............................................3 Roles...................................................11 4......................................................................................

SAP Best Practices Sales: Period End Closing Operations (203): BPD Sales: Period End Closing Operations 1 Purpose This scenario describes the collection of periodic activities in Sales & Distribution such as day ending activities or legal requirements like Intrastat and Extrastat reporting. Use the following master data in the process steps described in this document: Master / Org.. Comments See sections Business Conditions and Preliminary Steps. no Only use if you have activated the building block Serial Number Management (126). 2 Prerequisites You must have run through some SD scenarios so that some relevant data for closing issues has been created. Trading (reorder point planning) with serial numbers. data Material Value H11 Master / Org. See the sections Business See sections Business Conditions and Preliminary Steps.1 Master Data and Organizational Data SAP Best Practices Standard Values Essential master and organizational data was created in your ERP system in the implementation phase. data details Trading Good for Reg. Additional Master Data (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. no batch Material H20 Trading Good for Reg.. such as the data that reflects the organizational structure of your company and master data that suits its operational focus. no batch Material H12 Trading Good for Reg. For more information on how to create master data. Trading (reorder point planning) no Serial no. for example. © SAP AG Page 5 of 33 . see the Master Data Procedures documentation. and enables you to go through the process steps of this scenario. This master data usually consists of standardized SAP Best Practices default values. master data for materials. 2. Using Your Own Master Data You can also use customized values for any material or organizational data for which you have created master data. and customers. Trading (MRP planning) no Serial no. vendors.

Trading (reorder point planning) no Serial no.. Only use if you have activated the building block Batch Management (117). you must have completed the following processes and fulfilled the following business conditions before you can start going through this scenario: © SAP AG Page 6 of 33 . data details batch Comments Conditions and Preliminary Steps. with / w/o batch (FIFO strategy) Material Material Plant Storage Location Shipping Point Sales organizatio n Distribution channel Division D* S300 1000(1100) 1030/ 1040(1130/ 1140) 1000(1100) 1000 Service Materials Repair Material 10 10 2. batch controlled (FIFO strategy) Material F29 Finished Good MTS for Process Industry (PD planning) no Serial no. Date) Material F126 Finished Good MTS for Discrete Industry (PD planning) with Serial no.SAP Best Practices Sales: Period End Closing Operations (203): BPD Master / Org. See sections Business Conditions and Preliminary Steps. See sections Business Conditions and Preliminary Steps.2 Business Conditions The business process described in this Business Process Documentation is part of a bigger chain of integrated business processes or scenarios. with batch (Exp. See sections Business Conditions and Preliminary Steps. See sections Business Conditions and Preliminary Steps.. As a consequence. data Material Value Master / Org. See sections Business Conditions and Preliminary Steps. Trading (reorder point planning) no Serial no. Only use if you have activated the building block Batch Management (117). See sections Business Conditions and Preliminary Steps. Only use if you have activated the building block Batch Management (117).. Only use if you have activated the building block Serial Number Management (126). batch controlled (Exp.. H21 Trading Good for Reg. Date) Material H22 Trading Good for Reg.

Prerequisites The business roles have been assigned to the user who is testing this scenario. You only need these roles if you are using the NWBC interface.SAP Best Practices Sales: Period End Closing Operations (203): BPD Business condition You have completed all relevant steps described in the Business Process Documentation Prereq. The roles in this Business Process Documentation must be assigned to the user or users testing this scenario. Process Steps (154). Business role Employee (Professional User) Billing Administrator Technical name SAP_NBPR_EMPLOYEE_S Process step Assignment of this role is necessary for basic functionality. Review Blocked Sales Orders Review Log of Collective Invoice Creation Review Billing Due List Review Incomplete Sales Orders Review Sales Orders Due for Delivery Review Log of Collective Delivery Creation Review Log of Collective Delivery Creation Review Incomplete SD Documents (Deliveries) Review Sales Documents Blocked for Billing Review List Blocked (for accounting) Billing Documents Create Intrastat / Extrastat Calculation of Work In Process (Service Provider) SAP_NBPR_BILLING_S Sales Administrator Warehouse Clerk Sales Administrator SAP_NBPR_SALESPERSON_S SAP_NBPR_WAREHOUSECLERK_S SAP_NBPR_SALESPERSON_S Warehouse Manager SAP_NBPR_WAREHOUSEMANAGER_M Accounts Receivable Manager SAP_NBPR_AR_CLERK_M Customs Agent Product Cost Controller SAP_NBPR_CUSTOMSAGENT_S SAP_NBPR_PRDCOST_CONTRLR_S © SAP AG Page 7 of 33 . Scenario Prereq. You do not need these roles if you are using the standard SAP GUI. Process Steps (154) 2.3 Roles Use The following roles must have already been installed to test this scenario in the SAP Netweaver Business Client (NWBC).

02 Reviewing Sales Documents Blocked for Delivery Reviewing Sales Orders Due for Delivery Reviewing Log of Collective Delivery Creation Reviewing Incomplete SD Documents (Deliveries) Reviewing Outbound Deliveries for Goods Issue Reviewing VA14L VL10C V_SA Warehouse Manager V_UC Warehouse Clerk VL06O Billing Administrator V23 © SAP AG Page 8 of 33 .SAP Best Practices Sales: Period End Closing Operations (203): BPD Business role Technical name Process step Settling the Sales Order to Profitability Analysis (Service Provider) Excise Clerk SAP_NBPR_IN_EXCISECLERK_S Update Registers Extract Registers Monthly Utilization Generating ER1 Report 3 Process Overview Table Process step External process reference Busines s conditio n Business role Transacti on code Expected results Reviewing Blocked Sales Orders Reviewing Incomplete Sales Orders Billing Administrator (SAP_NBPR_BILLING_ S) Sales Administrator (SAP_NBPR_SALESP ERSON_S) Sales Administrator (SAP_NBPR_SALESP ERSON_S) Warehouse Clerk (SAP_NBPR_WAREH OUSECLERK_S) Warehouse Manager VKM1 V.

SAP Best Practices Sales: Period End Closing Operations (203): BPD Process step External process reference Busines s conditio n Business role Transacti on code Expected results Sales Documents Blocked for Billing Reviewing Billing Due List Reviewing Log of Collective Invoice Creation Reviewing List Blocked (for Accounting) Billing Documents Calculation of Work in Process (Service Provider) Settling the Sales Order to Profitability Analysis (Service Provider) Update for Initial Stock Upload Update for Stock Uploading from Production Update for Outgoing Entry Extract Registers Monthly Utilization Generating ER 1 Report Billing Administrator VF04 Billing Administrator V.21 Accounts Receivable Manager VFX3 Product Cost Controller KKAK Product Cost Controller VA88 Excise Clerk J1I5 Excise Clerk J1I5 Excise Clerk J1I5 Excise Clerk Excise Clerk Excise Clerk J2I5 J2IUN J2IER1 © SAP AG Page 9 of 33 .

Choose Save. Choose Back to return to the SAP Easy Access screen (SAP GUI). you review blocked sales orders and resolve any credit issues. Procedure 1. choose Environment → Credit Master Sheet. and resolve any credit issues that need to be handled.1. make the following entries: Field name Credit control area Credit account 3. To display the credit data for this customer. Choose Back.1 Process Steps Closing Operations 4. Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role 1. Select a sales order to be released. 9. 5. 4. 8.1 Use The sales order failed the credit check. Access the transaction choosing one of the following navigation options: Business role Billing Administrator (SAP_NBPR_BILLING_S) Description User action and values <Credit Control Area> 1000XX The relevant sold-to party Comment © SAP AG Page 10 of 33 . and then choose Release. In this activity. Analyze the credit information. 6. Access the transaction choosing one of the following navigation options: Option 1: SAP Graphical User Interface (SAP GUI) SAP ECC menu Transaction code Logistics → Sales and Distribution → Credit Management → Exceptions → Blocked SD Documents VKM1 2. 7. Select a sales order to review.SAP Best Practices Sales: Period End Closing Operations (203): BPD 4 4. On the screen. Reviewing Blocked Sales Orders Frequency Daily Prerequisites Sales orders are blocked due to credit check block. Choose Execute.

Choose the sales order number to view the sales order. and then choose Release.02 Orders ® 2.2 Use Reviewing Incomplete Sales Orders This activity displays a list of all incomplete documents that is based on the specified selection criteria. Result Sales orders that were blocked for credit reasons are now released when the customer situation meets the credit approval requirements. Choose Exit (Shift+F3) and confirm the Business client message with Yes to return to SAP Home (SAP NetWeaver Business Client). Make the following entries in the Documents Information section: Field name Description User action and values Comment © SAP AG Page 11 of 33 . 7. Select a sales order to be released. Direct Sales Product Division User action and values <Sales Organization> <Distribution Channel> <Division> Comment Sales Org Distribution Channel Division 3. 6. To display the credit data for this customer. Frequency Daily Procedure 1. go to the tab page All Customer Credits and enter the relevant search criteria. Select the customer and choose Customer Credit Management Display. Select the tab page All Credit Blocked Orders. 5.1. Maintain the search criteria (by choosing Change Query) as follows and choose Apply: Field name Credit control area Credit account Description User action and values <Credit Control Area> 1000XX The relevant sold-to party Comment 4.SAP Best Practices Sales: Period End Closing Operations (203): BPD Business role menu Sales → Credit Management 2. Access the transaction choosing one of the following navigation options: Option 1: SAP Graphical User Interface (SAP GUI) SAP ECC menu Transaction code Logistics ® Sales and distribution ® Incomplete Orders V. Select the tab page All Credit Blocked Orders. 4. 8. 3. Make the following entries in the Sales Organization data section: Field name Description Sales Org.

SAP Best Practices Sales: Period End Closing Operations (203): BPD Created by <blank> In order to select any incomplete sales order make no entries in this field. Select a sales order and choose Change. 9. 10.3 Use Reviewing Sales Documents Blocked for Delivery It shows sales orders that are on credit hold and need to be released by the credit department. 7. On the next screen choose Complete Data and the system will guide you to the incomplete entry. Maintain the missing details in the sales order. Select the Incompletion Log tab page to see what is missing in the sales order. 6. 4. 5. 8. Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role Business role Business role menu Sales Administrator (SAP_NBPR_SALESPERSON_S) Sales → Sales Orders → Sales Order Processing → Sales Documents Worklist 1. Result If no errors occurred the billing documents are created and the billing values are forwarded to Financial Accounting. Access the transaction choosing one of the following navigation options: Option 1: SAP Graphical User Interface (SAP GUI) © SAP AG Page 12 of 33 . 4. Frequency Daily Procedure 1.1. Choose Back. Choose Exit (Shift+F3) and confirm the Business client message with Yes to return to SAP Home (SAP NetWeaver Business Client). From the Active Queries of category Sales Orders choose the query Incomplete Orders (refresh the current query if necessary). select a sales order and choose Edit incompletion. Choose Back to return to the SAP Easy Access screen (SAP GUI). 5. Choose Execute. Maintain the missing details in the sales order and choose Save. 3. 2. 4. n the Incomplete SD Documents screen. Choose Save.

1.: Field name Created by: 3. On the screen Sales Documents Blocked for Delivery screen. Description User action and values * Comment * asterisk as wildcard Result A list of Sales Orders blocked for delivery as a result of credit check. Choose Execute. The transaction can either be processed repeatedly online or in batch during shipping hours. 4.4 Use Reviewing Sales Orders Due for Delivery Sales orders become due for delivery creation according to their schedule line. Choose Back to return to the SAP Easy Access screen (SAP GUI). Direct Sales Product Division User action and values <Sales Organization> <Distribution Channel> <Division> Comment Sales Org Distribution Channel Division 3.Data section: Field name Description Sales Org.SAP Best Practices Sales: Period End Closing Operations (203): BPD SAP ECC menu Logistics ® Sales and distribution ® Credit Management ® Sales and Distribution Documents ® Sales and distrib. Choose Exit (Shift+F3) and confirm the Business client message with Yes to return to SAP Home (SAP NetWeaver Business Client). SAP recommends to process the delivery due list at a minimum frequency of once a day. Choose Apply. Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role 1. © SAP AG Page 13 of 33 . make the following entries in the Organizat. 4. The schedule line becomes due for shipping. 4. From the Active Queries of category Sales Orders choose the query Orders Blocked for Delivery (refresh the current query if necessary). when the material availability and the transportation scheduling date for a schedule are reached. Access the transaction choosing one of the following navigation options: Business role Business role menu Sales Administrator (SAP_NBPR_SALESPERSON_S) Sales → Sales Orders → Sales Order Processing→ Sales Documents Worklist 2.documents blocked for delivery VA14L Transaction code 2. Frequency The frequency depends on the warehouse and shipping organization.

SAP Best Practices Sales: Period End Closing Operations (203): BPD Procedure Option 1: SAP Graphical User Interface (SAP GUI) 1. 4. Select your order and choose Creation in Background. Choose Exit (Shift+F3) and confirm the Business client message with Yes to return to SAP Home (SAP NetWeaver Business Client). On the Sales Order Item screen. 6. On the Delivery Due Orders page. Access the transaction choosing one of the following navigation options: SAP ECC menu Logistics → Logistics Execution → Outbound Process → Goods Issue for Outbound Delivery → Outbound Delivery → Create → Collective Processing of Documents Due for Delivery → Sales Order Items VL10C Transaction code 2. Access the transaction choosing one of the following navigation options: Business role Business role menu Warehouse Clerk (SAP_NBPR_WAREHOUSECLERK_S) Warehouse Management → Shipping → Outbound Delivery 2. Choose Execute. make the following entries: Field name Shipping point Delivery creation dates (From) Description User action and values 1000 <enter delivery creation date> The sales order item delivery date must be equal or greater than the delivery creation date (From) The sales order item delivery date must be equal or less than the delivery creation date (To) Comment Delivery creation dates (To) <enter delivery creation date> 3. 5. Set the Cursor on the line with the green light and choose the Details icon. 4. In the dialog box you see the number of the delivery which has been created. Select your sales order and choose Create Delivery in the Background. You can see message: Delivery <delivery number> created. make the following entries: Field name Shipping point 3. Choose Apply. Choose Back to return to the SAP Easy Access screen (SAP GUI). Description User action and values 1000 Comment © SAP AG Page 14 of 33 . 6. 5. Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role 1.

make the following entries: Field name Type of coll. Or Choose Exit (Shift+F3) and confirm the Business client message with Yes to return to SAP Home (SAP NetWeaver Business Client).SAP Best Practices Sales: Period End Closing Operations (203): BPD Result Sales orders that were due for delivery creation are now turned into deliveries. Use this log to identify the reasons and solve the issues. 4.5 Use Reviewing Log of Collective Delivery Creation This log provides the detailed reasons why a delivery creation has failed.1. To display the created delivery documents choose Documents. Frequency Daily Procedure 1. 4.) 5. If the creation fails. Access the transaction choosing one of the following navigation options: Option 1: SAP Graphical User Interface (SAP GUI) SAP ECC menu Logistics → Sales and Distribution →Shipping and transportation → Outbound Delivery → Lists and Logs → Collective Processing Log V_SA Transaction code Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role Business role Business role menu Warehouse Manager (SAP_NBPR_WAREHOUSEMANAGER_M) Warehouse Management → Warehouse Monitoring → Monitor Outbound Delivery Process → Analysis Collective Processing Outbound Deliveries 2. On the Log of Collective Run screen. (When the delivery documents created successfully. yesterday For example. Description User action and values L For example. there is no notes exist. 6. run On On 3. In order to display the log choose Notes. Choose Execute. a log entry will be generated. today Comment Deliveries from vl04 From date To date Result © SAP AG Page 15 of 33 . Choose Back to return to the SAP Easy Access screen (SAP GUI).

6 Use Reviewing Incomplete SD Documents (Deliveries) In this activity. On the Selection of Incomplete SD Documents screen. Sales Organization 3. Access the transaction choosing one of the following navigation options: Option 1: SAP Graphical User Interface (SAP GUI) SAP ECC menu Logistics → Sales and Distribution → Shipping and transportation → Outbound Delivery → Lists and Logs → Incomplete Outbound Deliveries V_UC Transaction code Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role Business role Business role menu Warehouse Manager (SAP_NBPR_WAREHOUSEMANAGER_M) Warehouse Management → Warehouse Monitoring → Monitor Outbound Delivery Process → List of Incomplete Outbound Deliveries 2. 4. you review sales orders that are not complete by using the applied incompletion procedure. 4. Description User action and values J <Sales Organization> Comment J – (Outbound) Delivery Result Outbound deliveries that were incomplete are now complete and may be processed further. Choose Execute. Choose Save. Maintain the missing details in the outbound delivery. Choose Back to return to the SAP Easy Access screen (SAP GUI). Frequency Daily Procedure 1. 7.SAP Best Practices Sales: Period End Closing Operations (203): BPD Sales orders for which the delivery creation failed are filed in this log. 6. On the Selection of Incomplete SD Documents screen. 5. Or Choose Exit (Shift+F3) and confirm the Business client message with Yes to return to SAP Home (SAP NetWeaver Business Client). © SAP AG Page 16 of 33 . make the following entries: Field name SD document categ.1. select a delivery and choose Change Document.

Mark the relevant delivery. The system issues the message Delivery xxxxxxxx was posted as a goods issue 7. 5. Expand Show Quick Maintenance or choose Change Query. Choose Back to return to the SAP Easy Access screen (SAP GUI).SAP Best Practices Sales: Period End Closing Operations (203): BPD 4. Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role 1. Access the transaction choosing one of the following navigation options: Option 1: SAP Graphical User Interface (SAP GUI) SAP ECC menu Logistics → Logistics Execution → Outbound Process → Goods Issue for Outbound Delivery → Outbound Delivery → Lists and Logs → Outbound Delivery Monitor VL06O Transaction code 2. Choose Post Goods Issue. (Choose today’s date on the dialog box) 7. 5. enter the Shipping Point / Receiving Pt: and choose Apply (refresh the current query if necessary). 3.1. Frequency Daily Procedure 1. Select your delivery. 6. Choose Execute. you review deliveries that are due for goods issue. On the Outbound Deliveries for Goods Issue screen. choose For Goods Issue. Choose Goods Issue. On the Outbound Delivery Monitor screen.7 Use Reviewing Outbound Deliveries for Goods Issue In this activity. Select the Due for Post Goods Issue tab page. 4. © SAP AG Page 17 of 33 . 3. Access the transaction choosing one of the following navigation options: Business role Business role menu Warehouse Clerk (SAP_NBPR_WAREHOUSECLERK_S) Warehouse Management → Shipping → Outbound Delivery Description User action and values <Shipping Point> Comment 2. make the following entries: Field name Shipping Point/Receiving Pt 4. 6. Choose Exit (Shift+F3) and confirm the Business client message with Yes to return to SAP Home (SAP NetWeaver Business Client).

make the following entries: Field name Entered by Description User action and values <blank> Comment No entry in order to select any blocked sales order regardless of creator. <Sales Organization> <Distribution Channel> <Division> The system may issue the information message. To change / remove the header billing block from the sales order choose Edit sales doc and make appropriate changes.1. 4. Or Choose Exit (Shift+F3) and confirm the Business client message with Yes to return to SAP Home (SAP NetWeaver Business Client). Choose Back to return to the SAP Easy Access screen (SAP GUI). Frequency Daily Procedure 1. Execute selection report SDSPESTA first. Use this log to identify the reasons and solve the issues. Sales organization Distribution channel Division 3. 5. 4. Confirm this message.8 Use Reviewing Sales Documents Blocked for Billing This log provides the detailed reasons why a delivery creation has failed. On the SD Documents Blocked for Billing screen. © SAP AG Page 18 of 33 . Choose Execute. Access the transaction choosing one of the following navigation options: Option 1: SAP Graphical User Interface (SAP GUI) SAP ECC menu Logistics → Sales and Distribution → Sales → Information System → Worklists → Sales Documents Blocked For Billing V23 Transaction code Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role Business role Business role menu Billing Administrator (SAP_NBPR_BILLING_S) Sales → Billing → Sales Documents Blocked For Billing 2.SAP Best Practices Sales: Period End Closing Operations (203): BPD Result The goods issue is posted.

4. Any message is displayed during processing of the individual document. enter the relevant search criteria and in the Documents to be selected area. and then choose Individual Billing Document.9 Use Reviewing Billing Due List When processing the billing due list. icons indicate whether or not a document has been billed successfully. After processing of the documents. Select the row with the sales order. Frequency Daily Procedure Option 1: SAP Graphical User Interface (SAP GUI) 1. 4. On the Maintain Billing Due List screen. You branch to transaction VF01 for every document selected. No combination is carried out. choose Order. c) Collective Billing Documents / Online © SAP AG Page 19 of 33 .1. It can also combine several deliveries in one invoice. b) Collective Billing Documents All documents marked in the billing due list are billed. To display the (Error) log. The system tries to condense them as much as possible. 6.SAP Best Practices Sales: Period End Closing Operations (203): BPD Result Sales orders that were blocked for billing may now be processed. Choose Back to return to the SAP Easy Access screen (SAP GUI). Delivery-related. Choose Display Bill List. Alternatively check activity “Review Log of collective invoice creation”. On the next screen select the relevant group and choose Notes. Choose Save. Access the transaction choosing one of the following navigation options: SAP ECC menu Transaction code Logistics → Sales and Distribution → Billing → Billing Document → Process Billing Due List VF04 2. Processing of the selected documents is carried out in the background.related. a) Individual Billing Documents An individual billing document is created for all documents marked in the billing due list. The system lists the documents to be invoiced on the basis of the selection criteria you enter. To display the created billing documents choose Documents. choose Log Display. 5. 3. you do not need to enter the individual documents to be invoiced. you return to the billing due list. Here.

4. The documents are condensed as far as possible according to the usual criteria. 5. Deliveryrelated. a) Individual Billing Document An individual billing document is created for all documents marked in the billing due list. expand Show Quick Criteria Maintenance or choose Change Query. On the Billing Due List tab page. Use this log to identify the reasons and solve the issues. Choose Exit (Shift+F3) and confirm the Business client message with Yes to return to SAP Home (SAP NetWeaver Business Client). Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role 1. Frequency Daily Procedure 1. Choose Apply.SAP Best Practices Sales: Period End Closing Operations (203): BPD The system branches to the Create billing document function (transaction VF01). b) Billing in Background All documents marked in the billing due list are billed. 6. Choose Save. Access the transaction choosing one of the following navigation options: Business role Business role menu Billing Administrator (SAP_NBPR_BILLING_S) Sales → Billing 2. No combination is carried out. enter the relevant search criteria and choose Order. 4. 3.1. Select the sales order.related. Result If no errors occurred the billing documents are created and the billing values are forwarded to Financial Accounting. and then choose Individual Billing Document. Processing of the selected documents is carried out in the background. Access the transaction choosing one of the following navigation options: Option 1: SAP Graphical User Interface (SAP GUI) SAP ECC menu Logistics → Sales and Distribution → Billing → Billing © SAP AG Page 20 of 33 .10 Use Reviewing Log of Collective Invoice Creation This log provides the detailed reasons why an invoice creation has failed. The system tries to condense them as much as possible. Any message is displayed during processing of the individual document.

run On On 3. Frequency Daily Procedure 1. Access the transaction choosing one of the following navigation options: Option 1: SAP Graphical User Interface (SAP GUI) SAP ECC menu Logistics → Sales and Distribution → Billing → Billing Document → Billing → Billing Document → Blocked Billing Docs VFX3 Transaction code Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role © SAP AG Page 21 of 33 . yesterday For example.1. Choose Execute. To display the (Error) log choose Notes.make the following entries: Field name Type of coll. Choose Back to return to the SAP Easy Access screen (SAP GUI).SAP Best Practices Sales: Period End Closing Operations (203): BPD Documents → Log of Collective Run Transaction code V. Description User action and values F For example. Or Choose Exit (Shift+F3) and confirm the Business client message with Yes to return to SAP Home (SAP NetWeaver Business Client). Use this list to identify the reasons and solve the issues. 5. To display the created billing documents choose Documents.21 Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role Business role Business role menu Billing Administrator (SAP_NBPR_BILLING_S) Sales → Billing → Log of Collective Run 2. On the Log of Collective Run screen. 4.. 6.11 Reviewing List Blocked (for Accounting) Billing Documents Use This log provides the detailed reasons why a billing document is blocked for accounting. 4. today Comment Invoices from vf04 From date To date Result Sales orders / deliveries for which the billing creation failed are filed in this log.

1. From date To date Comment Created On Created On 3. make the following entries: Field name Sales organization Created By Description User action and values <Sales Organization> <blank> No entry in order to select any blocked sales order regardless of creator. Choose Back to return to the SAP Easy Access screen (SAP GUI). 5. Procedure 1. Or Choose Exit (Shift+F3) and confirm the Business client message with Yes to return to SAP Home (SAP NetWeaver Business Client). On the Release Billing Documents for Accounting screen. yesterday For example. In order to display the (Error) log choose Notes. 6.SAP Best Practices Sales: Period End Closing Operations (203): BPD Business role Business role menu Accounts Receivable Manager (SAP_NBPR_AR_CLERK_M) Accounts Receivable → Postings → Billing → Release Blocked Billing Documents to Accounting 2. Access the transaction choosing one of the following navigation options: Option 1: SAP Graphical User Interface (SAP GUI) SAP ECC menu Logistics → Sales and Distribution → Sales → Product Cost by Sales Order → Period-End Closing → Single Functions → Results Analysis → Execute → Collective Processing KKAK Transaction code Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role Business role Product Cost Controller (SAP_NBPR_PRDCOST_CONTRLR_S) © SAP AG Page 22 of 33 . Select a billing doc to be released and then choose Release to Accounting.12 Use Calculation of Work in Process (Service Provider) Results analysis is used to evaluate the progress of sales orders on the basis of planned and actual revenues and costs. Choose Execute. today 4. For example. Result Billing documents that were blocked are now released respectively the reason why they are still blocked is reported. 4.

Enter 1000 in the Controlling Area field and choose Enter. YBC2. choose Start Immediately. Choose Check. YBC3. 4. Choose Background Processing in the Processing Options. YBR1 Comment Use Function Multiple Selection to enter the relevant sales document type Enter Current period in place of closed period Enter Current period in place of closed period Closed period <current year> RA Version Execution Type Test run 0 Choose option Calculate Deselected To review WIP without calculation.SAP Best Practices Sales: Period End Closing Operations (203): BPD Business role menu Product Cost Controlling → Periodic Processing → Results Analysis → Actual Results Analysis: Sales Ordrs 2. YBO1. the system displays the Set Controlling Area dialog box. Log Information Messages Output object list Hide orders with 0 Value Selected Selected Selected 4. The first time you access this transaction. 3. Or Choose Exit (Shift+F3) and confirm the Business client message with Yes to return to SAP Home (SAP NetWeaver Business Client). 3. On the Background Processing Options dialog box. 5. 2. On the initial screen enter the following data: Field name Sales Document Type Calculation to period Fiscal year Description User action and values YBC1. Note the job number. Choose Execute. – Not recommended because of possible long runtime. and then choose Execute. Choose Confirm. Recommendation Run this process in the background: 1. © SAP AG Page 23 of 33 . select this checkbox. Choose Back to return to the SAP Easy Access screen (SAP GUI).

7.13 Settling the Sales Order to Profitability Analysis (Service Provider) Use The settlement process moves all revenues from the sales order to a controlling object for profitability analysis. select it and then select the Own Jobs line. Frequency Settlement can occur on a periodic basis during the life of a sales order and/or upon completion of all work.1. 6. and then choose Continue. Result The system generates a report of WIP calculations for the selected sales orders. Choose from the top of the screen the System. Procedure 1. 3. Access the transaction choosing one of the following navigation options: Option 1: SAP Graphical User Interface (SAP GUI) SAP ECC menu Transaction code Logistics → Sales and Distribution → Sales → Order → Subsequent Functions → Settlement VA88 Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role Business role Business role menu Product Cost Controller (SAP_NBPR_PRDCOST_CONTRLR_S) Product Cost Controlling → Periodic Processing → Settlement → Actual Settlement: Sales Orders 2. The first time you access this transaction. make the following entries: Field name Sales Document Settlement Description Number of sales document to be settled Period to be settled User action and values Leave blank to settle all relevant sales orders Current period Comment © SAP AG Page 24 of 33 . Choose Joblog to see the results. the system displays the Set Controlling Area dialog box. 8. 4. Enter 1000 in the Controlling Area field and choose Enter. Use the activity 4. choose Jobname. On the Actual Settlement: Sales Orders screen. Prerequisites Settlement can occur on a periodic basis during the life of a sales order and/or upon completion of all work. On the Job Overview screen.12 for the Service Scenarios.SAP Best Practices Sales: Period End Closing Operations (203): BPD 5. On the Background Print Parameters dialog box. choose the Output device.

the excise authorities require you to maintain (update) the following registers relating to excise duty RG1 . With classification ROP and RMA 1. But you need to maintain (update) with other movement types if it is being used For Ex. Frequency End of the month (Once in a month) Procedure 4. RG23D. Or Choose Exit (Shift+F3) and confirm the Business client message with Yes to return to SAP Home (SAP NetWeaver Business Client).. Note the results on the subsequent screen Actual Settlement: Sales Documents Basic List. 5. etc. Use After Creating Excise Invoice (J1IIN) . And it helps to keep record of all receipts and issues related to excisable materials. 162. Choose Execute. Choose Back to return to the SAP Easy Access menu. 4. Movement types 101.2 Update Registers The steps Update Register.Then Process will be.202. 123. 161. 201.SAP Best Practices Sales: Period End Closing Operations (203): BPD Field name Period Fiscal Year Test Run Description Year to be settled Key for simulation User action and values Current year Deselect Comment 4.2.1 Update for Initial Stock Upload Prerequisites When material coming from MIGO. but if needed process flow should follow. Choose Back to return to the SAP Easy Access screen (SAP GUI). Extract and Utilization are not prerequisite for ER 1 Report . 102. RG23C. 261. 6. 262. As per Indian Law. Result You have successfully settled the sales order revenues to the profitability analysis. Access the transaction choosing one of the following navigation options: Option 1: SAP Graphical User Interface (SAP GUI) SAP ECC menu J1ILN(India Localization Menu) → Indirect Taxes → © SAP AG Page 25 of 33 . 122. RG23A. Movement Type 561 (Initial Stock Upload). PLA.

2. 5. Again select line and choose Create. Access the transaction choosing one of the following navigation options: Option 1: SAP Graphical User Interface (SAP GUI) © SAP AG Page 26 of 33 . 4. 561 ROP X RG1 Select from RG 23RG 1 Tab Choose F8 (Execute). Choose Back to return to the SAP Easy Access screen (SAP GUI). Please choose Continue to confirm the Register dialog if any. Repeat step 5-6 for all of records. 7. Or Choose Exit (Shift+F3) and confirm the Business client message with Yes to return to SAP Home (SAP NetWeaver Business Client). 6. Select Line and choose Simulate (That line will be green).SAP Best Practices Sales: Period End Closing Operations (203): BPD Registers → Excise Tax→ Update RG23A/C Issues and RG1 Transaction code J1I5 Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role Business role Business role menu 2.Choose Enter to skip the warning messages.2 Update for Stock Uploading from Production Prerequisites When Stock is updating from production (confirmation). Select these fields Field name Company Plant Excise Group Posting Date Description User action and values 1000 1000 Choose For One Month End Date should not be the date in the future Comment Excise Clerk (SAP_NBPR_IN_EXCISECLERK_S) CIN→ Register Creation For RG23 and RG1 Movement Type Classification Document Entry Date Registers 3. Procedure 1. 8. 4. Movement Type 101.

Select these fields Field name Company Plant Excise Group Posting Date Description User action and values 1000 1000 21 For One Month Comment Chose Chose Chose Excise Clerk (SAP_NBPR_IN_EXCISECLERK_S) CIN→ Register Creation For RG23 and RG1 End Date should not be the date in the future Movement Type Classification Document Entry Date Registers 3. 6. 7. 4. Choose Enter to skip the warning messages. 5.3 Update for Outgoing Entry Prerequisites When Stock is going outside (PGI). 4. Movement Type 601. Repeat step 4-5 for all of records.2. Access the transaction choosing one of the following navigation options: Option 1: SAP Graphical User Interface (SAP GUI) SAP ECC menu J1ILN(India Localization Menu) → Indirect Taxes → © SAP AG Page 27 of 33 . Or Choose Exit (Shift+F3) and confirm the Business client message with Yes to return to SAP Home (SAP NetWeaver Business Client). Choose Back to return to the SAP Easy Access screen (SAP GUI). Procedure 1. 101 RMA x RG1 Select from RG 23RG 1 Tab Choose F8 (Execute).SAP Best Practices Sales: Period End Closing Operations (203): BPD SAP ECC menu J1ILN(India Localization Menu) → Indirect Taxes → Registers → Excise Tax→ Update RG23A/C Issues and RG1 J1I5 Transaction code Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role Business role Business role menu 2. Select Line and choose Simulate (That line will be green) Again select line and choose Create..

once entries are updated in wrong Indicator of Receipt or Issue. Result Successfully register will get updated. 601 IDH . 5. Repeat step 4-5 for all of records. Choose Back to return 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). Select these fields Field name Company Plant Excise Group Posting Date Description User action and values 1000 1000 21 For One Month Comment Chose Chose Chose Excise Clerk (SAP_NBPR_IN_EXCISECLERK_S) CIN→ Register Creation For RG23 and RG1 End Date should not be the date in the future Movement Type Classification Document Entry Date Registers 3. 6. Select Line and choose Simulate (That line will be green). 7. Again select line and choose Create. of records). IWE . Choose Enter to skip the warning messages. © SAP AG Page 28 of 33 .SAP Best Practices Sales: Period End Closing Operations (203): BPD Registers → Excise Tax→ Update RG23A/C Issues and RG1 Transaction code J1I5 Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role Business role Business role menu 2. If register is not updated properly then you can not extract those registers. the same can not be reversed and will have a impact on accounting in Excise Registers. x RG1 IDH for domestic sale IWE for Export sale Select from RG 23RG 1 Tab Choose F8 (Execute). 4. (Processing over for xxx no. Utmost care has to be taken while updating the Registers.

ll / PLA / RG23D / RG1 Select one by one and execute or at a time those you need to extract.. Comment or 51 Chose Chose 3. Frequency Procedure End of the month (Once in a month) Procedure 1. RG23C. © SAP AG Page 29 of 33 . 4. RG23D. If already extracted. choose yes button. Need to Extract RG1 . PLA registers. Access the transaction choosing one of the following navigation options: Option 1: SAP Graphical User Interface (SAP GUI) SAP ECC menu Transaction code J1ILN(India Localization Menu) → Indirect Taxes → Registers → Excise Tax→ Extract J2I5 Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role Business role Business role menu 2. You can also Display the last extracted date. Choose Back to return to the SAP Easy Access screen (SAP GUI). ll / RG23C PART l. and system will overwrite the data. This activity is performed to summarize all updated entries. RG23A. Or Choose Exit (Shift+F3) and confirm the Business client message with Yes to return to SAP Home (SAP NetWeaver Business Client). Excise Clerk (SAP_NBPR_IN_EXCISECLERK_S) CIN→ Extract On the Excise Registers Extraction screen.SAP Best Practices Sales: Period End Closing Operations (203): BPD 4. system will ask for confirmation of Re-Extraction. Choose Continue to confirm the Register dialog.3 Extract Registers Use After Updating Registers. make the following entries and choose Execute: Field name Excise group Start date End date Select Registers Registers Description User action and values 21 from to Select any Registers RG23A PART l.

make the following entries: Field name Company Code Plant Excise Group Period From To Pay Cen from Cen& Ser tax CR Description User action and values 1000 1000 21 <First day of current month> <Current Date> Select Comment Chose Chose Chose 3. © SAP AG Page 30 of 33 .e. It is monthly activity which will be done by the first week of every month (I. We can do Utilization Before extract or after extract the Registers.4 Monthly Utilization Use After Updating Registers. Frequency Procedure End of the month (Once in a month) Procedure 1. On the Monthly Utilization screen.SAP Best Practices Sales: Period End Closing Operations (203): BPD Result Registers successfully Extracted System will display the register extracted with OK button. utilization done for the Previous month). ECS. CENVAT utilization refers to utilizing the Excise duties which we have availed during Purchase (i. 4. for the Raw Materials) in RG23A/C register against the Excise payable at the time of sales. Choose Execute and you will get three duties (BED. Access the transaction choosing one of the following navigation options: Option 1: SAP Graphical User Interface (SAP GUI) SAP ECC menu Transaction code J1ILN(India Localization Menu) → Indirect Taxes → Sales/Outbound Movements → Fortnightly Payment J2IUN Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role Business role Business role menu Excise Clerk (SAP_NBPR_IN_EXCISECLERK_S) CIN→ Monthly utilization 2. SECS) and these all are in red cross. If register is not updated properly then you can not extract those registers and system will display with ‘x’ red mark and register name.e.

Extract and Utilization are not prerequisite but if needed process flow should follow. Frequency Procedure End of the month (Once in a month) Procedure 1. the steps Update Register. Then choose simulate I-con (button). Choose Save. That red cross will become green. To Run ER 1 Report. Access the transaction choosing one of the following navigation options: Option 1: SAP Graphical User Interface (SAP GUI) SAP ECC menu N/A © SAP AG Page 31 of 33 . 1000) and enter.SAP Best Practices Sales: Period End Closing Operations (203): BPD 4. mansion amount in utilized column (For EX. by all the assesses (as defined under Central Excise Act) on a monthly basis for production and removal of goods and other relevant particulars and CENVAT credit. choose select duty tab so you can see utilization for ECS. 8. Choose Back to return to the SAP Easy Access screen (SAP GUI). 100) and enter. E. Now select second line. 50) and enter. Extracting Registers and Utilization. choose select duty tab so you can see utilization for BED. Then select third line. mansion amount in utilized column (For EX. and you can check these posted document in this transaction code (FB03).ECS & SECS) against the Excise Payable accounts ( Excise duty Payable at the time of Sales). 6. Select first line item.R. Using the above transaction we utilize the the Purchase side Excise accounts ( BED.5 Generating ER 1 Report Use After Updating. choose select duty tab so you can see utilization for SECS. you can generate ER 1 Report which is excise monthly return for availing CENVAT. Result You have done CENVAT utilization successfully. You are saving this document means posting. That red cross will become green. mansion amount in utilized column (For EX. 5. 4.-1 to be filled with excise authorities. 7. That red cross will become green. 9. Or Choose Exit (Shift+F3) and confirm the Business client message with Yes to return to SAP Home (SAP NetWeaver Business Client).

which you can take to reverse some of the activities described in this document.1 Appendix Reversal of Process Steps In the following section. To: Last day of current month. 4. you can find the most common reversal steps. make the following entries: Field name Excise group Plant Report Period Description User action and values 21 1000 From – To Comment Chose Chose From: First day of current month. i. Or Choose Exit (Shift+F3) and confirm the Business client message with Yes to return to SAP Home (SAP NetWeaver Business Client).e. On the initial screen. Monthly Return which is need to be submitted to Excise Authorities every month end.SAP Best Practices Sales: Period End Closing Operations (203): BPD Transaction code J2IER1 Option 2: SAP NetWeaver Business Client (SAP NWBC) via Business Role Business role Business role menu Excise Clerk (SAP_NBPR_IN_EXCISECLERK_S) CIN→ Monthly ER1 Report 2. Result Now ER 1 fulfills requirement. Details Select one by one 3. Select one by one option from Details tab and Choose Execute and get a print for this. Review Blocked Sales Orders Transaction code ( SAP GUI) Reversal: Transaction code ( SAP GUI) Business role Business role menu Comment Create Intrastat / Extrastat VKM1 Review Blocked Sales Orders VKM2 Billing Administrator Sales → Credit Management → Released SD Documents © SAP AG Page 32 of 33 . Choose Back to return to the SAP Easy Access screen (SAP GUI). 5 5.

SAP Best Practices Sales: Period End Closing Operations (203): BPD Transaction code ( SAP GUI) Reversal: Transaction code ( SAP GUI) Business role Business role menu Comment Actual Settlement Sales Orders Transaction code ( SAP GUI) Reversal: Transaction code ( SAP GUI) Business role Business role menu Comment ENGR Change Intrastat / Extrastat ENGR Customs Agent Foreign Trade → Foreign Trade/Customs → Periodic Declarations VA88 Actual Settlement: Sales Orders VA88 Product Cost Controller Product Cost Controlling → Periodic Processing → Settlement → Actual Settlement: Sales Orders Select menu: Settlement → Reverse © SAP AG Page 33 of 33 .