SAP Credit Management How To Guide: Enhance

CreditPaymentRecord (Kreditvektor) with customer fields

Date: 02-11-2004

Scope:
Calculate and send new Field ZFIELD from FI-AR client to CR Server and use
the field in in the formulas for calculation

In the AR Client.

1a) Change Sender Record 46c and 4.7 (Enterprise)

• In 4.6C and 4.7C you have to append the field to UKM_S_VECTOR. This
structure is use to send the table via RFC.

1b) Generate Proxy (Release ERP)

• In ERP Systems you have to use the integration builder first. -> go to the
XI section
• When XI steps are done
SPROXY to generate proxies
DatatypeEnhancement:
• the append is now visible in UKM_CREDIT_PAYMENT_RECORD

2) Badi UKM_FILL
Consider 2 options for data calculation and collection:
• calculation on the fly - when the transfer to XI is done (Badi UKM_FILL) in
Report UKM_TRANSFER_VECTOR. This is reasonable for data already
stored somewhere and are easily readable (the keys company code and
customer are available in the Badi).
• store extra data in table UKM_TRANSFER_ARV by a customer report.
Process the data with the Badi UKM_FILL. This table offers different data
types, the standard report calculates and rebuilds the types
01 Oldest Open Item
02 Last Payment
03 Highest Dunning Level
04 Key Figure/Amount with Currency
You can store extra data in type 5 onwards and have to use the Badi to
map your data to the transfer structure or proxy.
The report will read and delete all entries during the transfer (also the
customer entries)

IN the CR Server
1) Create Append for UKMBP_VECTOR_IT
Use structure UKM_S_BP_VECTOR_INDEX to append the table. Reason: in
method CONDENSE VECTOR, the data from different systems are
condensed. This works for the three parts of the vector, therefore the Append
has to be in one of them.

2) Use BDT to show the append

• create new function group
• code events ISSTA ISDST DLVE1 as function units
• create screen containing the new fields as display only fields
• enter the new function as Events TA BUS7
• new fieldgroup for the new fields USE 2600-2799 for customer extensions
• create new view - assign screen and function module
• create new section
• enter section into Screen UKM210
NB: you cannot maintain the Vector data during BP maintenance, but you
should be able to display it.

Use the client copy TA to copy the BDT settings to another client (Ta SCC1)

3) Generate Proxy
• -> see in the XI section
• When XI steps are done
SPROXY to generate proxies
DatatypeEnhancement:
• the append is visible in UKM_CREDIT_PAYMENT_RECORD

4) Badi UKM_VECTOR_PUSH
after XI is done: enhance the inbound message: In CL_UKM_XI_FACADE
the badi is called to convert the input data and map them to ukmbp_vector_it.

Activities in XI

In SLD
1) Steps for 4.6c and 4.7 clients (usage of RFC modules)
• create new Product
• create two new Software products
• e.g. <mycompany>FINBASIS ) contains Mapping (FINBAIS300)
• e.g. <mycompany>ERP2004 (from ERP2004 containing the RFC
module)
Define Dependencies to FINBASIS 300 and set the context to
'InstallationTime'

Repository:
1) Datatype extension
• create datatype extension eg CreditPaymentRecordExtension
UkmVectorPush_CreditPaymentRecordNotification
use the same name in Abap and XI e.g. (Z_RATIOL)
• activate the change list

2) Steps for 4.6c and 4.7 clients (usage of RFC modules)

• use tools->import from SLD->import SW component to import the two new
components
• create namespace e.g. http://<mycompany>.com/xi/FSCM for Finbasis
(the Mapping)
allow import of RFC interfaces to import the append structure from the
sender
Import Objects -> Import RFC (right mouseclick) -> logon to the client system -> all RFC
modules are displayed -> mark UKM_VECTOR_PUSH
• activate the change list
• Message Mapping: Copy the mapping from Finbasis300 into your SW
component (eg <mycompany>finbasis)
In case you data extension is missing import the RFC again
How to copy: (right mouse on source -> copy, select your SW component -> then select
the namespace , do not mark 'Save original as reference'
Drop the function unit into the mapping - then the new fields are available
• Use the 'graphical mapping' to map the new fields
• Interface Mapping: do the same as for the message mapping (no need for
field mapping)
• activate the change list

Configuration
1) Steps for 4.6c and 4.7 clients (usage of RFC modules)
• Receiver determination:..UKM_VECTOR_PUSH
Change the Name of the Mapping file to your own file (your name space)
• Interface determination: replace the existing interface with yours (your
name space)
Service: ... Interface: UKM_VECTOR_PUSH
configured Inbound if:CreditPayment..

• Change Communication Channel (e.g. Add some comment) to force

the RFC Adapter to refresh its data with the new structure (look in cache :
Otherwise the message : field zz.. is not defined in ukm_t_... appears
.Use SM58 to check the trfc msgs)

• Check that the Cache Notification were processed. (In case a red light
appears, you have to restart the J2ee engine - see note 730570 for RFC
FAQ)

Formula builder
• add field in UKM_S_BP_CUSTOMER_EXTENSION
• implement method FILL_FIELDS of BADI UKM_BP_ADD_FIELDS
• implement method ADD_FIELDS of UKM_EV_FORMULA
Objects Checklist
Ar Client
Package ___________

Append UKM_S_VECTOR ___________

Badi UKM_FILL ___________

CR Server
Package ___________

Append UKM_S_BP_INDEX ___________

Badi UKM_VECTOR_PUSH ___________

BDT
Function Group ___________

Screen ___________

...EVENT_ISSTA ___________

...EVENT_ISDST ___________

...EVENT_DVLE1 ___________

Fieldgroup/View/Section ___________

XI-SLD
Product ___________

SW Package Mapping ___________

SW Package Plugin ___________

XI-Repository
Namespace ___________

Message Mapping ___________

XI-Configuration
Receiverdetermination ___________

Interfacedetermination ___________

Channel ___________