Some of the most important fields for BP Counterparty role (TR0151) are ->
There is no LTMC or LSMW template available to update this data.
Maintaining this data is tedious task, especially when it must be done for many BPs. (eg – migrating data from ECC to S4HANA).
KCLJ program can assist to perform the mass upload with help of Z-structures.
Steps to follow ->
Step 1 -> Create Z structures
Create three different Z-structures with help of developer as below ->
Component | Component Type | Data Type | Length | Decimal | Coordinate | Short Description |
AKTYP | BU_AKTYP | CHAR | 2 | 0 | 0 | Activity Category |
RLTP1 | BU_PARTNERROLECAT | CHAR | 6 | 0 | 0 | BP Role Category |
ROLE1 | BU_PARTNERROLE | CHAR | 6 | 0 | 0 | BP Role |
ROLE2 | BU_PARTNERROLE | CHAR | 6 | 0 | 0 | BP Role |
CHIND_9 | BU_CHIND | CHAR | 1 | 0 | 0 | Change category |
PARTNER | BU_PARTNER | CHAR | 10 | 0 | 0 | Business Partner Number |
TYPE | BU_TYPE | CHAR | 1 | 0 | 0 | Business Partner Category |
BPKIND | BU_BPKIND | CHAR | 4 | 0 | 0 | Business Partner Type |
BU_GROUP | BU_GROUP | CHAR | 4 | 0 | 0 | Business Partner Grouping |
FIBUKRS | BUKRS | CHAR | 4 | 0 | 0 | Company Code |
CHIND_SI3 | BU_CHIND | CHAR | 1 | 0 | 0 | Change category |
RANTYP_A3 | RANTYP | CHAR | 1 | 0 | 0 | Contract Type |
SANLF_A3 | SANLF_DI | CHAR | 3 | 0 | 0 | Product Category |
SGSART_A3 | VVSART | CHAR | 3 | 0 | 0 | Product Type |
SFHAART_A3 | TB_SFHAART | CHAR | 3 | 0 | 0 | Financial Transaction Type |
AUTHOR | TB_AUTHOR | CHAR | 1 | 0 | 0 | Authorization indicator for Treasury product |
Component | Component Type | Data Type | Length | Decimal | Coordinate | Short Description |
AKTYP | BU_AKTYP | CHAR | 2 | 0 | 0 | Activity Category |
RLTP1 | BU_PARTNERROLECAT | CHAR | 6 | 0 | 0 | BP Role Category |
ROLE1 | BU_PARTNERROLE | CHAR | 6 | 0 | 0 | BP Role |
ROLE2 | BU_PARTNERROLE | CHAR | 6 | 0 | 0 | BP Role |
CHIND_9 | BU_CHIND | CHAR | 1 | 0 | 0 | Change category |
PARTNER | BU_PARTNER | CHAR | 10 | 0 | 0 | Business Partner Number |
TYPE | BU_TYPE | CHAR | 1 | 0 | 0 | Business Partner Category |
BPKIND | BU_BPKIND | CHAR | 4 | 0 | 0 | Business Partner Type |
BU_GROUP | BU_GROUP | CHAR | 4 | 0 | 0 | Business Partner Grouping |
FIBUKRS | BUKRS | CHAR | 4 | 0 | 0 | Company Code |
CHIND_SC1 | BU_CHIND | CHAR | 1 | 0 | 0 | Change category |
WAERS_C1 | BP_WAERS_DI | CHAR | 5 | 0 | 0 | Currency Key |
ZAHLVID_C1 | TB_ZAHLVID | CHAR | 10 | 0 | 0 | Identification of Payment Details (Standing Instructions) |
BVTYP | TB_RPBANK | CHAR | 4 | 0 | 0 | Partner Bank Details |
HBKID_C1 | HBKID | CHAR | 5 | 0 | 0 | Short key for a house bank |
HKTID | HKTID | CHAR | 5 | 0 | 0 | ID for account details |
ZLSCH | DZLSCH | CHAR | 1 | 0 | 0 | Payment Method |
UZAWE_C1 | UZAWE | CHAR | 2 | 0 | 0 | Payment method supplement |
SZART | TB_SZART | CHAR | 1 | 0 | 0 | Payment Transaction |
RPZAHL | TB_RPZAHL_NEW | CHAR | 10 | 0 | 0 | Payer/payee |
SPAYRQ | TB_SPAYRQK | CHAR | 1 | 0 | 0 | Generate Payment Request |
SPRSNG | TB_SPRSNGK | CHAR | 1 | 0 | 0 | Individual Payment |
SPRGRD | TB_SPRGRD | CHAR | 1 | 0 | 0 | Determine Grouping Definition |
SCSPAY | TB_SCSPAY | CHAR | 1 | 0 | 0 | Same Direction Necessary for Joint Payment? |
ZWELS_C1 | DZWELS | CHAR | 10 | 0 | 0 | List of Respected Payment Methods |
Component | Component Type | Data Type | Length | Decimal | Coordinate | Short Description |
AKTYP | BU_AKTYP | CHAR | 2 | 0 | 0 | Activity Category |
RLTP1 | BU_PARTNERROLECAT | CHAR | 6 | 0 | 0 | BP Role Category |
ROLE1 | BU_PARTNERROLE | CHAR | 6 | 0 | 0 | BP Role |
ROLE2 | BU_PARTNERROLE | CHAR | 6 | 0 | 0 | BP Role |
CHIND_9 | BU_CHIND | CHAR | 1 | 0 | 0 | Change category |
PARTNER | BU_PARTNER | CHAR | 10 | 0 | 0 | Business Partner Number |
TYPE | BU_TYPE | CHAR | 1 | 0 | 0 | Business Partner Category |
BPKIND | BU_BPKIND | CHAR | 4 | 0 | 0 | Business Partner Type |
BU_GROUP | BU_GROUP | CHAR | 4 | 0 | 0 | Business Partner Grouping |
FIBUKRS | BUKRS | CHAR | 4 | 0 | 0 | Company Code |
CHIND_SI1 | BU_CHIND | CHAR | 1 | 0 | 0 | Change category |
WAERS_A1 | BP_WAERS_DI | CHAR | 5 | 0 | 0 | Currency Key |
RANTYP_A1 | RANTYP | CHAR | 1 | 0 | 0 | Contract Type |
SANLF_A1 | SANLF_DI | CHAR | 3 | 0 | 0 | Product Category |
SGSART_A1 | VVSART | CHAR | 3 | 0 | 0 | Product Type |
SFHAART_A1 | TB_SFHAART | CHAR | 3 | 0 | 0 | Financial Transaction Type |
SSIGN | TB_SSIGN | CHAR | 1 | 0 | 0 | Direction of Flow |
ZAHLVID | TB_ZAHLVID | CHAR | 10 | 0 | 0 | Identification of Payment Details (Standing Instructions) |
Step 2 - Add the Z-structures using KCLL transaction
Step 3 – Create the file with data in same format as of the structure, and execute KCLJ transaction to upload data using txt file –
Below is example of uploading authorization data.
This saved lot of my time, hope you find it helpful too.
Thanks,
Nilesh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
14 | |
10 | |
7 | |
7 | |
5 | |
5 | |
4 | |
4 | |
3 | |
3 |