SAP ABAP IMG Activity _ISUUTDE_000067 (Make Basic Settings)
Hierarchy
☛ IS-UT (Software Component) SAP Utilities/Telecommunication
   ⤷ IS-U (Application Component) SAP Utilities
     ⤷ EE80 (Package) IS-U: Customizing
IMG Activity
ID _ISUUTDE_000067 Make Basic Settings  
Transaction Code S_KK4_82001167   (empty) 
Created on 20021219    
Customizing Attributes _ISUUTDE_000067   Make Basic Settings 
Customizing Activity _ISUUTDE_000067   Make Basic Settings 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name _ISUUTDE_000067    

Use

In this IMG activity you make the basic settings for bill and payment advice note processing within the scope of Intercompany Data Exchange.

Here, you define how a bill or payment advice note can be structured and processed.

You use the individual subdialogs for the following purposes:

  • Permitted Bill Lines / Payment Advice Note Lines

    You maintain all the permitted line types here (for documents).

    For every line type, you have to decide whether it is a posting-relevant line type, or an info line.

    As a rule, only posting-relevant line types are included for processing processes.

    You can also specify between a prepayment and a budget billing.

    This is important, for example, to be able to differentiate between normal bill lines and budget billing lines in document processing.

    In order to prevent any ambiguity during the bill creation and further processing, you should use each line type only once in the Permitted Line Type per Bill section.

    Example:

    Line type 1 describes a posting-relevant bill line, which deals with a prepayment.

  • Permitted Document Types

    You maintain all permitted document types here (for different bill types / payment advice note types).

    For each document type you can specify which of the following it is:

    • Bill
    • Payment advice note
    • Request for prepayment
    • Bill reversal
    • Reversal of a request for prepayment

      You must also specify the meaning of the internal ID.

      In order to prevent any ambiguity when creating or processing line types , you should use each line type only once in the Permitted Document Type per Bill Type section.

      Example:

      Document type 1 describes a grid usage bill. Within the grid usage bill, the point of delivery is used for identification. The document is from the Billing type.

  • Permitted Bill Types

    You maintain the permitted bill types and payment advice note types here.

    Specify which bill category / payment advice note category it is. You have the following options here:

    • Single bill
    • Aggregated bill
    • Payment advice note
    • Complaint

      You must also specify which identification function is used for the header data ID. Corresponding identification functions are already stored in Customizing, in the activity Define Process Control (Part 1), and can be enhanced there.

      Specify what type the sender and recipient are (for example, IS-U service provider). For each bill type / payment advice note type you can specify a function module, which reads the application-specific parameters. The function module should have the interface from the sample module INV_INVOICE_EXAMPLE_PARAM_001. You can use function module ISU_DEREG_PARAM_INV_INBOUND as a sample implementation.

      The following process types are available for each bill type / payment advice note type:

      1. Identification (of end customer)

      2. Check Before Data Transfer

      3. Data Transfer

      4. Check After Data Transfer

      5. Transfer of Data

      6. Complaint

      For each bill type / payment advice note type you can use the corresponding indicator to specify whether the process step Identification, Check After Data Transfer, Data Transfer and Check After Data Transfer are to be omitted.

      You can also override the description of the process types in the processing log for the documents. This means that you can change the descriptions of the process types.

      Example:

      The bill type / payment advice note type '1' describes a grid usage bill for single customers. The bill is from the single bill category. The sender and recipient are to be IS-U service providers, who are to be determined using the identification module '1000' (Determine Service Provider). Parameters different to those in Customizing are to be determined using function module ISU_DEREG_PARAM_INV_INBOUND. No process steps are to be omitted.

Enter the following, dependent data for the permitted bill types / payment advice note types:

  • Permitted document type for each bill type / payment advice note type
    • Here, you specify which document types are permitted for a bill type / payment advice note type. You also specify a function module, which can generate a reversal document from the corresponding document.
    Example:
    The document type Grid Usage Bill (document type '1') is to be permitted for grid usage bills (bill type / payment advice note type '1'). The function module ISU_DEREG_INV_REVERSAL generates a corresponding reversal document from this bill.
  • Permitted Line Type per Bill Type

    You define which line types are permitted for a bill type here.

    You can also specify whether the lines are relevant for transfer and what these lines contain (such as normal bill lines/payment advice note line, totals line, deduction line, final amount line, additional quantity information, additional prepayment information).

    • Example:
    Line type '1' (bill line) is permitted for grid usage bills (bill type / payment advice note type '1') and document type '1' (grid usage bill). This bill line is not relevant for transfer, and corresponds to a normal bill line. In contrast, line type '5' (final amount of bill) is relevant for transfer, as this is to be transferred to contract accounts receivable and payable or accounts payable accounting. This transfer takes place in the process step Transfer of Data.
  • Permitted Processes Per Bill Type / Payment Advice Note Type
    • Here, you specify the permitted processes for each bill type / payment advice note type, for each document type, and for each process type. The selection of processes is stored in Customizing, in the following activities:
    Define Process Control (Part 1)
    Define Process Control (Part 2)
    Example:
    For process type Complaint, the following processes are permitted for grid usage bills (bill type / payment advice note type '1') and document type '1' (grid usage bill):
    - Process '6000' (no complaint)
    - Process '6001' (bill complaint and payment advice note processing)
    - Process '6002' (bill complaint)
    You can use these three processes in a service provider agreement.
  • Processes per Bill Type / Payment Advice Note Type
    • Here, you specify the individual processes that are to be executed for each bill type/payment advice note type, document type and process type. In addition, you can specify how the processes are to be overridden at application level.
    Example:
    Process '6001' (invoice complaint and payment advice note processing) is specified for the process type complaint, for grid usage bills (bill type / payment advice note type '1') and document type '1' (grid usage bill). This process is used if no service provider agreement (that overrides this process) between the sender and recipient of the bill.

  • Definition of Release Level

    You maintain the release level here if bills are to be released manually.

  • Type of References

    References can exist for a bill or a payment advice note. You maintain the permitted types of reference here.

    For each reference type, you must specify a function module that is used to display the reference.

    Example:

    You can use function module INV_DISPLAY_REFERENCE_IDOC to display the reference type '1' with the description Reference to IDoc.

  • Customer Action in Monitoring

    In monitoring for bill and payment advice note data it is possible to include customer-specific actions. You create those actions here. For each action, you must specify a function module that executes the action.

Requirements

Standard settings

Activities

Example

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_000067 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_CUST2 C - View cluster SM34 Make Basic Settings 
History
Last changed by/on SAP  20021219 
SAP Release Created in 471