Show TOC

Storing Incoming Documents with Bar CodesLocate this document in the navigation structure

Use

When storing with bar codes, the incoming document is assigned a bar code label either before it is entered or when it is entered. The bar code must be transferred when the business object is posted.

Note

For information on the general process for early and late storing with bar codes, see Storage Scenarios with Integration of Bar Code Technology.

You can also perform storing with bar codes using the Generic Object Services (see Assigning an Object the Bar Code of a Document).

Integration

As well as connecting to the Generic Object Services (see above), you can also integrate storing with bar codes explicitly into your SAP application by integrating the function module ARCHIV_BARCODE_GLOBAL.

The function module ARCHIV_BARCODECHECK_(name of bar code type) is also available.

In ArchiveLink administration and in the IMG, you can define new bar code types and determine whether to carry out a bar code check for them. This function module performs the check. The bar code ID is transferred and a return code expected, where a return codes = 0 indicates that the bar code is correct. A non-zero value indicates an error.

The SAP System provides a bar code check for the following bar code types as standard (see Customizing Bar Code Scenarios):

  • 2/5_I (2/5 interleaved)

  • EAN_8 (EAN 8)

  • EAN_13 (EAN 13)

  • UPC_A (UPC A)

  • UPC_E (UPC E)

    Caution

    Only the check digits are checked and not the semantics of the bar code.

Integration of ARCHIV_BARCODE_GLOBAL

IMPORTING

AR_OBJECT

NO_DOC_CHANGE

&DEFAULT&

SPACE

OBJECT_ID

SAP_OBJECT

UPDATETASK

&DEFAULT&

SPACE

NO_CHECK

&DEFAULT&

SPACE

NO_POPUP

&DEFAULT&

SPACE

BARCODE

&DEFAULT&

SPACE

The function module does the following:

  • Calls a dialog box in which the user enters the bar code. For this, the parameter NO_POPUP must have the value SPACE. If the parameter has the value X, no dialog box is displayed. This is preferable for processing batch-input sessions, for example.

  • If the NO_CHECK parameter has the value X, there is no check as to whether bar code entry is active for the user. However, an entry containing the object type transferred must be made in administration in each case.

  • Enters the bar code and the corresponding application-related object key in the link table.

The parameter NO_DOC_CHANGE determines whether it is possible for the user to change the document type in the dialog box.

The parameter UPDATETASK determines whether the entry in the link table is made in the update task or in dialog.