Generating SD Orders

Procedure

  1. On the initial screen choose Start of the navigation path Logistics Next navigation step Equipment and Tools Management Next navigation step Transaction Data Next navigation step Settlement Next navigation step SD Orders Next navigation step Create SD Orders End of the navigation path .

  2. The Input ETM Sales Orders with Job Split in R/3 SD screen appears.

    Note Note

    The system fills the Settlement date field with a value corresponding to the last settlement date from Customizing, the Max. no. of items per order field with a default value of 10 and the No. of jobs to be started field with a default value of 10. If more than one batch job is to be run, you should enter the number in the No. of jobs to be started field. If you process parts of data in parallel, you can minimize the total run time dramatically. You can change the default values.

    End of the note.

  3. Enter the appropriate values. If you enter a document number as well as a ship-to party and company code, the system ignores the document number. A warning appears. If you select your data using the document number, you must remove/not enter a ship-to party or company code. Confirm the warning and continue processing.

  4. The selection buttons program start as test run or as update run control whether it is a test or update settlement run.

    Caution Caution

    You should always run a Test without orders before you run an update run.

    End of the caution.

    You can settle materials and equipment separately if you have not selected using the ship-to party or the company code.

  5. Set either Yes or No for Orders sorted by GR . If you select Yes, only items from a goods recipient are created per automatically generated SD order (can be used for example by work cooperatives). If you select No the standard ETM order generation occurs. This means that each order item can be a different goods recipient.

  6. By entering a value for Number of Orders per Commit Work you can determine the number of order headers per commit work. In the case of an incorrect settlement this saves you time because you only have to run the incorrect orders again.

  7. Choose Execute.

    If you have not performed or not completed a location setup, a dialog box appears informing you of this. If this is the case, execute a Location Setup and repeat the SD settlement procedure.

    Note Note

    Start of the navigation path If a split job in settlement is terminated you can process the remaining data to be processed by using restart (transaction SE38 Next navigation step Program J_3GINVC_RESCUE). End of the navigation path Enter the same selection criteria in the input fields as in the original settlement start (pay special attention to Update run / Test run .

    End of the note.

Result

SD orders have been generated. You can now process these SD orders. You can find further information on this subject under Changing and Displaying SD Orders .

After completing the SD order generation you have to perform a postprocessing run to update the status ( Start of the navigation path Logistics Next navigation step Equipment and Tools Management Next navigation step Transaction Data Next navigation step Settlement Next navigation step SD Orders Next navigation step Postprocess Input End of the navigation path ) If during the first postprocessing run the system does not update all statuses (for example because of a lock by another user) you have to trigger another run.

Note Note

Release 4.6C2 has an improved settlement lock concept. Double-start of the update run is not possible. The required lock is set at the start of the program and released at the end. The lock remains during program termination. In this case to unlock the run you have to use program J _3GINVC_RESCUE (transaction Start of the navigation path SE38 Next navigation step Program J_3GINVC_RESCUE End of the navigation path )

End of the note.