SAP ABAP IMG Activity FISL_PS_GBEB_PRCS (Define Business Transaction Variants)
Hierarchy
☛ BBPCRM (Software Component) BBPCRM
   ⤷ CRM (Application Component) Customer Relationship Management
     ⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
       ⤷ FBAS (Package) Financial accounting 'Basis'
IMG Activity
ID FISL_PS_GBEB_PRCS Define Business Transaction Variants  
Transaction Code S_AL0_96000709   (empty) 
Created on 20020116    
Customizing Attributes ACC_SL_PS_K_U_A   Special Ledger, Actual Postig: Optional Activity, Uncritical 
Customizing Activity FISL_PS_GBEB_PRCS_OB   Define Business Transaction 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name FISL_PS_GBEB_PRCS_DC    

Use

In this activity you can define business transaction variants for the document split business transactions.

This is useful for the following purposes:

  • For a business transaction, you have defined exactly which item categories can be posted. With a business transaction variant you can restrict the business transaction further by excluding further item categories from those permitted. When you post a document, the system can check, using the business transaction variant, whether the posting is permitted. If an item category is not permitted, the system rejects the posting.
  • For each business transaction variant, you define the rule according to which the document is to be split. If you also want to split individual documents for one business transaction according to different rules, you have to define the required number of business transaction variants.

Note:

When you define a variant, you also have to define the relevant Split Rules.

You assign the business transaction variants to a document type in the activity Classify Document Types for Document Split.

Requirements

You have defined your own splitting method.

Standard settings

In the standard, SAP delivers business transactions with permitted item categories. SAP also delivers business transaction variants for the business transactions.

You cannot define your own business transactions. However, you can define your own business transaction variants that restrict the business transactions further.

In the respective document split procedures, standard split rules are assigned to the business transaction variants delivered. These rules follow a defined meaning. Before you activate the document split, you should check to what extent these rules are suitable for the business processes to be posted.

Activities

  1. Select the business transaction for which you want to create a business transaction variant and then double-click on Business Transaction Variant in the navigation area.
  2. Choose New Entries.
  3. In the field Variant, enter a four-digit key and a name for your business transaction variant.
  4. The system automatically transfers the item categories and the basic setting of the business transaction.
  5. Select the business transaction variant and double-click on Item Categories Assigned in the navigation area.
  6. You can make the following settings for the item categories:
    • Not supported
      • If you set this indicator, the item category is not permitted for this business transaction category. You should prohibit the item categories that are not to be used for this business transaction variant. For example, in an asset invoice, only the item category Asset is to be posted; the expense is not to be posted.
    • Mandatory
      • If you set this indicator, this item category must exist when you post a document. Set the item categories as obligatory if the business process and/or its logic require this item category. For example, a customer invoice must contain a customer, since the leading company code is derived from the customer line item in the subsequent processes.
    • Once Only
      • If you set this indicator, the item category must only appear once in the business transaction specified.

      Note
      You do not have to make a setting for every item category.

  7. Save your business transaction variant.

Example

In the standard, SAP delivers the business transaction Customer Invoice. The item categories for this business transaction are defined as follows:

Cat.    Name    Not supported    Obligatory    Once Only

01000    Balance sheet account

01100    Company code clearing

02000    Customer        X

05100    Tax on sales/purchases

05200    Withholding tax

07000    Asset

20000    Expense

30000    Revenue

40200    Exchange rate difference

80000    Budget

Business Attributes
ASAP Roadmap ID 203   Establish Master Data 
Mandatory / Optional 2   Optional activity 
Critical / Non-Critical 2   Non-critical 
Country-Dependency A   Valid for all countries 
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
GBEB_PROCESS_VARIANT C - View cluster SM34  
History
Last changed by/on SAP  20020430 
SAP Release Created in 470