SAP ABAP IMG Activity _ISUUTDE_000068 (Define Process Control (Part 1))
Hierarchy
☛ IS-UT (Software Component) SAP Utilities/Telecommunication
   ⤷ IS-U (Application Component) SAP Utilities
     ⤷ EE80 (Package) IS-U: Customizing
IMG Activity
ID _ISUUTDE_000068 Define Process Control (Part 1)  
Transaction Code S_KK4_82001168   (empty) 
Created on 20021219    
Customizing Attributes _ISUUTDE_000068   Define Process Control 
Customizing Activity _ISUUTDE_000068   Define Process Control 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name _ISUUTDE_000068    

Use

In this IMG activity you define how the bill or payment advice note data is processed.

You either enter the bill and payment advice note data manually, or it is imported by means of an IDoc or BAPI.

Once you have entered the data, you can execute the following processes:

  • Identification of data
  • Check before data is copied
  • Data transfer (to IS-U)
  • Check after data is copied
  • Export of data (to FI-CA)
  • Complaint

    This process has a special setting, as it is only relevant when the document status is changed to To Complain and a reason for complaint is added. Function modules for the complaint are defined in Customizing, in the activity define process control (part 2).

  • Reversal

    This process has a special setting, as it is only relevant when the document status is changed to To Reverse and a reversal reason is added. Function modules for the reversal processing are defined in Customizing, in the activity Make Basic Settings for permitted document types for each bill and payment advice note type.

  • Manual processing

Manual Processing does not require you to make any Customizing settings.

Requirements

Standard settings

Activities

You can save certain basic data, such as check modules, for the individual processes:

  • Identification of data

    Identification modules

    Here, you can specify which function modules can be used for identification purposes. The identification can be divided into two parts:

    • Identification of header data
      • The sender and the recipient of the bill and payment advice note data are identified in this step. If you want to use the function module to identify the header data, you must select the FuMo Used for Identification of Header Data field.
    • Identification of Document Data/Line Data
      • The individual end customers are identified in this step.

The processes Check Before Data is Copied, Copy Data, Check After Data is Copied and Transfer of Data have the same structure.

It is however possible to specify the function modules that execute the action and give them a general key. The individual actions are then grouped together for processing at a later stage.

Each of these groups consists of a header and the corresponding subprocesses.

You can specify the following data at header level:

You can specify the following data at subprocess level:

  • Run number
  • Key of subprocess to be executed
  • Flag, whether an error terminates the process
  • Flag, whether subprocesses can be hidden

Example

The identification number '1000' is used to determine the function module for identifying the service provider (sender/recipient) ISU_DEREG_INV_IDENT_010. The indicator Ident.HD is set, as header data for a bill or payment advice note is to be identified here.

This identification number is used in Customizing, in the activity Make Basic Settings to determine service providers within permitted bill/payment advice note types.

The identification number '1001' is used to determine the function module for identifying the end customer ISU_DEREG_INV_IDENT_020. Within the function module the internal point of delivery identification, and thus the internal business partner number, are determined. This is done, for example, using the external point of delivery identification (which, for example, was transferred in an IDoc). This identification number is then used in Customizing, in the activity Make Basic Settings within the permitted processes for the process type Identification of Data, and within the processes for each bill / payment advice note.

The function module ISU_DEREG_INV_CHECKB_010 with the check module number '2001' and the description Supply Scenario at Point of Delivery is defined, for example, as the Check Module Before Transfer. Because the module only checks the current document with a view to the supply scenario at the point of delivery, the All Documents indicator is not set.

The group '2001' with the description Supply Scenario Check is, for example, maintained as the Check Group Before Transfer to Header. Within the group, no status of the check group is to be determined using the customer-specific module. For this reason, the corresponding fields are not maintained. If you branch from the header data to the Check Group Before Transfer, you can define which check modules are to be run in what order within the check group.

The check group number can then be used in Customizing, in the activity Make Basic Settings within the permitted processes for the process type Check Before Data Transfer, and within the processes for each bill/payment advice note.

Business Attributes
ASAP Roadmap ID 204   Establish Functions and Processes 
Mandatory / Optional 2   Optional activity 
Critical / Non-Critical 2   Non-critical 
Country-Dependency A   Valid for all countries 
Assigned Application Components
Documentation Object Class Documentation Object Name Current line number Application Component Application Component Name
SIMG _ISUUTDE_000068 0 SK40000003 Intercompany Data Exchange 
Maintenance Objects
Maintenance object type C   Customizing Object 
Assigned objects
Customizing Object Object Type Transaction Code Sub-object Do not Summarize Skip Subset Dialog Box Description for multiple selections
VC_INVRCPT_CUST C - View cluster SM34 Define Process Control 
History
Last changed by/on SAP  20030521 
SAP Release Created in 471