19.09.2016 Views

Transportation Management with SAP LES

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

17<br />

Goods Issue<br />

Figure 17.7 Detailed Information in the Document Header<br />

The document header only provides a few statistical details, that is, when, by<br />

whom and at what date the goods issue document was created. The Trans./Ev.<br />

Type “WL” is fixed and identifies this posting document as a goods issue posting.<br />

Actual Goods Issue Date<br />

You have the option to specify the date of the goods issue in the delivery document.<br />

If there is a delay, for example, and you are unable to perform the GI posting<br />

until a few days after, you can specify the actual goods issue date in the header<br />

of the delivery document. This means that the material document has three dates:<br />

the creation date (when your material document was created), the goods issue date<br />

(when your materials left the plant), and the posting date (the posting period in<br />

which your posting is made to the G/L accounts).<br />

17.1.2 Performing Goods Issue Posting Collectively<br />

In many cases, you may have many delivery documents per day for which you<br />

want to perform goods issue posting. It would be too time-consuming to perform<br />

posting individually for each of these delivery documents. Collective processing<br />

is the solution if you need to perform goods issue manually for several delivery<br />

documents simultaneously.<br />

Selecting the Delivery Documents<br />

Collective processing provides you <strong>with</strong> various options for selecting the delivery<br />

documents for which goods issue posting needs to be performed (see Figure 17.8).<br />

You can, for example, enter a shipment document number so that the system dis-<br />

532<br />

© 2014 by Galileo Press Inc., Boston (MA)

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!