/AIN/CL_DEV_CREATE_EPC_WRITE - EPC Generation activity

RFUMSV00 - Advance Return for Tax on Sales/Purchases   Addresses (Business Address Services)  
This documentation is copyright by SAP AG.

Functionality

This activity creates EPC to be used by printing activity subsequently.

The activity may have following four parameters:

• EPC_FILTER_VALUE: Filter value of new EPC

• EPC_TYPE: Type of new EPC

• PREVENT_REISSUE: Stop rule if tag is already existing

• PREVENT_NEW_TAG: Stop rule if the tag has not been observed in AII before

When the activity is called during a mobile message processing, the EPCs must be present in the message. These EPCs are transferred to the activity context with Action Object Status = 'EW'.

When the activity is called during a fixed reader message, following steps are performed:

• The activity checks to see if EPC exists, and if it does, the EPC is transferred to the activity context.

• If the EPC is not present in the message and the EPC_TYPE in the rule is set to SGTIN-64 or SGTIN-96

• the activity checks if a GTIN is present within the message. If the activity finds the GTIN in the message, it encodes epc based on this GTIN.

• otherwise it looks for a product (PRODUCT) and unit of measure (UOM) in the message. If they are present it derives the GTIN from it and then encode the EPC

• otherwise, If there is a document assigned to the device group, it checks if a GTIN is maintained for the document. If yes, then it encodes the EPC based on that GTIN.

• If the EPC is not present in the message and the EPC_TYPE is set to GRAI-64 or GRAI-96, the behaviour is the same as that in the case of SGTIN-64 or SGTIN-96

• If the EPC is not present in the message and the EPC_TYPE is set to SSCC-64 or SSCC-96

• the activity checks if SSCC is present in the message. If so, it uses this SSCC to encode the EPC.

• otherwise, if a company prefix (COMPANY_PREFIX) is present in the message, it uses that to generate an SSCC and encodes an EPC

• otherwise, it gets the company prefix from the location ofthe device.

• If the EPC is not present in the message and the EPC_TYPE is set to one of GIAI-64, GIAI-96, DOD1-64, DOD1-96, then the behaviour is same as that in the case of SSCC-64 and SSCC-96.

• If EPC is encoded correctly, the EPC is transferred to the activity context with Action Object Status = 'EW'. Otherwise, it exits with error

• In case of fixed reader messages, the activity then replaces the device and device group guids withthat of the assigned printer device and device group guids. If no printer is assigned to the reader device, the activity exits with error.

Relationships

This activity should be succeeded with the printing activity /AIN/CL_DEV_PRINT_TAG.

Example

Notes

This activity may be used in rules that are used by mobile message or fixed reader message.

Further information

RFUMSV00 - Advance Return for Tax on Sales/Purchases   General Data in Customer Master  
This documentation is copyright by SAP AG.


Length: 3370 Date: 20120526 Time: 040528     triton ( 113 ms )