SAP ABAP IMG Activity SIMG_CGJB01JBLC15 (Transfer Category 013: Business Partners)
Hierarchy
☛ EA-FINSERV (Software Component) SAP Enterprise Extension Financial Services
   ⤷ IS-B-DP (Application Component) Transaction Data Pool
     ⤷ JBDC (Package) Customizing IS-B Data Pool
IMG Activity
ID SIMG_CGJB01JBLC15 Transfer Category 013: Business Partners  
Transaction Code S_ABA_72000076   IMG Activity: SIMG_CGJB01JBLC15 
Created on 19990121    
Customizing Attributes SIMG_CGJB01JBLC15   Transfer Category 013: Business Partners 
Customizing Activity    
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name SIMG_CGJB01JBLC15    

General Information on Transfer Category 'Business Partner' in SAP Banking

The transfer category 'business partner' only refers to a section of all the existing business partner tables. Most significantly, the name and one or more addresses of the business partner can be transferred. The transfer takes place using header/item structures. Note that this transfer does NOT have all the functions available with online entry. This is because the complete checks made during online entry are not made here. For example, no fixed value checks for fields with fixed values are carried out, which means that you need to check online whether the transferred records are correct and can be displayed.

The receiver structure is formed from table JBIUPART. The tables in the datapool filled by this structure are BP000, BP030 and SANS1.

Validity

In addition to the transfer category 'SAP Banking Business Partner' (category=13), there are other transfer categories (category=14 + 15) that process a business partner. From Release 4.62, the business partner changes from category=13 to category=15. It is important you read the corresponding Release Notes on this matter. You can find the documentation about transfer category 15 in the IMG under Cross- Application Components -> SAP Business Partner -> External Data Transfer -> General Information -> Transfer Categories -> Transfer Categories Business Partner.

In the area of SEM Banking, you have the following options for converting the Treasury Business Partner (TR-BP) to the SAP Business Partner:

1. The previous external data transfer of TR-BP using transfer category 13 will still be used. All data is saved exclusively in the TR-BP tables. There is no parallel update to the SAP-BP tables. As various transactions require SAP-BP, it is necessary to call up the conversion report after each transfer involving category 13. This transfers all relevant changes from TR-BP to SAP-BP. You can apply the second alternative at any time in place of the first alternative. We recommend you convert from transfer category 13 to transfer category 15 because transfer category 13 will only be maintained in the medium term.

2. The former external data transfer of TR-BP using transfer category 13 is no longer used. Instead, only transfer category 15 is used. This updates data in TR-BP at the same time as in SAP-BP. Previously, the conversion report had to be run once for all existing TR-BPs.

Up to Release 4.61, the following rules applied when using SEM PA in conjunction with SA and RA:

Business partners are always transferred using transfer category 13. For additional information, that is required in SA and RA, read the following documentation.

Header and Item Structure

SAP Banking identifies the header and item records as follows: If field 'ADR_REF_K' is blank, the record is a header. If this field is not blank, it is an item.

Conventions

  • Required fields

    Required fields for header and items: GROUP_ID, PARTNR/EXTPARTNR.

    Required fields for items only: ADR_DAT, ADR_D_E, ADR_REF_K.

    Required fields for headers only: ADR_REF, BUKRS, ADR_REF_K must not be set.

    You also need to consider the fields specified in the field control in Customizing to be required fields. These fields need to be transferred in both the header and item records.

    You cannot transfer a single header without any items. In any case, it is not helpful to do so since no address is assigned to the header. You should therefore make sure this does not happen.

  • Default address

    During online entry, you always specify one address as the 'default address'. In external data transfer, the data must be delivered in such a way that the default address appears online. Note the following:

    • In a header, field ADR_REF is a required field. Precisely one of the delivered items must have the same value in field ADR_REF_K as the value in the header field ADR_REF. This is not checked by SAP Banking, which means you have to check the fields yourself.
    • Mode field SFEMODE determines whether an Insert or an Update is carried out. When a header is updated, the new header must be transferred in its entirety. For both Update and Insert, headers need to be delivered directly before the corresponding items. Items are always inserted and never updated. This is because, based on the concept for business partner transfer, resetting the validity date replaces the existing item with a new item. SAP Banking automatically sets the end date ADR_D_E to 31.12.9999. This ensures that the business partner history is saved.
    • For a current or new entry, ADR_D_E must not be filled. SAP Banking enters 31.12.9999 in this field. Per business partner, and per ADR_REF_K only one current or new item may be delivered in each transfer. In the case of first transfers, however, several older items may be transferred if they are transferred together with a current item. All item entries must be delivered in such a way that there are no gaps between the specified dates. No item identical to an existing item may be delivered.

Special Features

  • If the partner is a natural person, NAME_LAST and NAME_FIRST must be filled; ORG_NAME and ORG_NAME2 must be blank.
  • For organizations, ORG_NAME and ORG_NAME2 must be filled and NAME_LAST and NAME_FIRST must be blank.
  • Validation

    Validation is always set to level 3.

  • Number ranges

    You can select both internal and external number assignment for number range object 'BP_PARTNR' for business partner transfer.

    If you want to select internal number assignment, you must deliver the external partner number EXTPARTNR. Field PARTNR remains empty.

    With external number assignment, field PARTNR must contain the external number. Field EXTPARTNR is optional. PARTNR and EXTPARTNR have to be delivered the same for all records for a partner. PARTNR has to be delivered with leading zeros.

    During data transfer, the type of number assignment used depends on the allocation made in the business partner grouping within Customizing. This grouping must be specified in the field GROUP_ID.

    The items are linked to the header by an internally assigned number, which makes referencing possible. Make sure that the number range object 'FVV_ADRNR' and the number range 'P1' are maintained.

    A business partner may only be processed once per transfer. A record that is added may never be updated later on during the transfer process as this could lead to a sudden termination of the transfer.

  • Roles

    For specific requirements, you can transfer role categories and roles when transferring the partner. To do this, you can specify one or more roles in the header record as well as in the flow record. If the number of required roles/role categories exceeds the number of delivered header and item records for a business partner, you will not be able to transfer all roles/role categories for the business partner.

    When a role is delivered, the system assumes it has an insert indicator.

    The fields required for transferring the role are taken from table BP1000. The deletion indicator is used with field DEL_INDRO. Provision is not made for deleting the roles of a partner. Instead, archiving is used.

    You need to ensure that the same role is not transferred twice for a businss partner within a transfer. This would lead to an inconsistant dataset.

If all roles are required, for example to enable the execution of Treasury functions, you have the possibility of controlling this with an indicator (SALLROL=1). You can only set this indicator in the header, and it cannot be used together with a role in the header. If you have existing partners with several roles, and want to create the remaining available roles, you simply deliver the header in update mode with SALLROL=1.

  • Transaction authorizations

    Each transferred partner is assigned maximum transaction authorization. This authorization is valid for the delivered company code. The same procedure as for business partner roles applies, except that SALLGPB=1 has to be delivered instead of SALLROL. This assigns all transaction authorizations for all company codes. If no company code is specified, then no transaction authorizations are created.

  • Relevance for Bank Profitability Analysis

    For each business partner, you need to define for which application it is relevant. To do this, you have to set field SEGUB for every application and for each individual record respectively, which means for header and item records.

Business Attributes
ASAP Roadmap ID 308   Transfer Data to Live System 
Mandatory / Optional 2   Optional activity 
Critical / Non-Critical 1   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 SIMG_CGJB01JBLC15 0 I070004706 External Data Transfer 
Maintenance Objects
Maintenance object type    
History
Last changed by/on SAP  19990928 
SAP Release Created in