SAP ABAP Data Element ADDI_OPER (Follow-up action for procedure for additionals)
Hierarchy
☛ BBPCRM (Software Component) BBPCRM
   ⤷ LO-ADM (Application Component) Additionals Management
     ⤷ WTAD (Package) IS-R: Additionals
Basic Data
Data Element ADDI_OPER
Short Description Follow-up action for procedure for additionals  
Data Type
Category of Dictionary Type D   Domain
Type of Object Referenced     No Information
Domain / Name of Reference Type CHAR2    
Data Type CHAR   Character String 
Length 2    
Decimal Places 0    
Output Length 2    
Value Table      
Further Characteristics
Search Help: Name    
Search Help: Parameters    
Parameter ID   
Default Component name    
Change document    
No Input History    
Basic direction is set to LTR    
No BIDI Filtering    
Field Label
  Length  Field Label  
Short 9 FolUpAct 
Medium 11 Fol-up Actn 
Long 37 Follow-up action, proc. for addits. 
Heading 11 Foll-upActn 
Documentation

Definition

Action to be triggered for an additional due to an event in an application.

Use

Follow-up actions determine which transactions are to be carried out for an additional. Possible follow-up actions are:

  • Empty: information purposes only

    You use this follow-up action if you simply want to enter a reference to an additional in a reference document but no other operation is to be linked to this.

This follow-up action is useful for outline agreements, for example. The additionals are therefore listed in the purchasing document, but no follow-up actions are required.

  • 1: Generate additionals IDoc immediately

    An additionals IDoc is generated immediately upon posting of a transaction. In the case of purchase orders for materials, an IDoc is sent to the vendor. In the case of goods movements and deliveries, an IDoc is sent to the plant concerned.

  • 99: Generate an additionals IDoc immediately (in the dialog database transaction)

    For follow-up action "1" an additionals IDoc is prepared and sent within the posting of a reference document. This process can take too long if additionals data in, for example, labeling is to be available very quickly (for example, in labeling). You can then use a follow-up action in which the IDoc can be prepared before it is posted.

    Note:

    • This follow-on action has a negative effect on system performance.
  • 2: Generate purchase order for additionals

    A document is updated based on the follow-up action. The subsequent purchase order is actually generated using a seperate application.

  • 3: Wait on external IDoc request

    This follow-up action is useful if the partner processing the reference document (for example, the vendor) is to specify the best time to process the additional.

    The manufacturer of a T-shirt requests the data on the tickets to be attached to the T-shirts at a point in time that fits best into his production process.

    Data is requested by calling a BAPI.

  • 8: Generate additionals IDoc from delivery message (output)

    A series of messages is usually generated for deliveries. These messages are processed using transaction "VL71". In order for tickets, forexample, can be printed at this point, a message must previously have been generated in the delivery. The generation of this message causes a follow-up action.

  • 98: Generate additionals IDoc when generating an transport order.

    An additionals IDoc is generated when a transport request is created if an additionals document with this follow-on action is contained in the delivery item referenced by the transport request. The system must, therefore, be constructed so that such a document is created when the delivery is entered.

  • 85: Supplementary Logistics Service (for example, pre-picking).

    This function controls generation and checking from data relevant to picking within merchandise distribution. The following fields from table "TWT_ACTION" are used in particular cases.

    • Follow-on action "85" is relevant for merchandise distribution.
    • Sub-items should be generated.
    • The item category in sales documents should be SLSV.
    • The relevance of SLS is checked in goods movements using module "W_VAS_GR_CHECK_HINT".
    • Packing rules are checked using the function module "W_VAS_DELIVERYPACKING_CHECK_PP".
    • Packing rules are displayed using the module "W_VAS_DELIVERY_DISPLAY_MESSAGE".
    • An enhancement of service-dependent data is not planned.
    • The generation of a new subitem is triggered by the module "W_VAS_CPO_PP_ORDERS".
    • Module "W_VAS_CPO_PP_ORDERS_SORT" serves to sort deliveries when generating sub-items for a collective purchase order.
    • You can use these settings if you want to create your own follow-on actions for Supplementary Logistics Services.

Which data is analyzed for additionals in the Retail Information System (RIS) is controlled by follow-up actions. A separate follow-up action has been defined for purchasing, goods movements, and deliveries.

  • 4: RIS: Update as sales order

    Entered as application "sales order" in RIS.

  • 5: RIS: Update as purchase order

    Entered as application "purchase order" in RIS.

  • 6: RIS: Update as goods movement

    "Goods movement" entered as application.

  • 7: RIS: Update as delivery

    The additional is classified as being relevant for a delivery.

    If you want additionals data to be identified in the RIS as a delivery, you have to assign follow-up action "7" for the procedure for additionals to the goods movement associated with the delivery. The system then processes a goods movement (usually a goods receipt). In RIS, however, the values for the additional are managed as a delivery.

None of the follow-up actions defined for RIS should be entered for deliveries when maintaining control parameters for a procedure for additionals.

History
Last changed by/on SAP  19990310 
SAP Release Created in