Ansicht
Dokumentation

RJGAUF00 - IS-M: Transfer BP Data (Roles GP,KU,EW,JZ,MK) with Address Changes

Fill RESBD Structure from EBP Component Structure BAL Application Log Documentation
This documentation is copyright by SAP AG.

Description

This report enables you to generate a batch input session for use in importing address changes. The entry in field JPARVW (function key) determines the type of address data.

The data for import is taken from a text file in a directory that is accessible to the application server.

The data must be stored record by record and in the form of one of the data structures listed below in this file (Details on Creating a Text File).

In some cases, particularly when making changes to existing data, it is not possible to tell whether the old value in fields that are initialized is not to be changed or deleted. You must either enter the old value in fields that are not to be changed or the symbol you enter for the No Data indicator on the selection screen. Fields in the data record for which the 'No Data' indicator is selected are ignored when the batch input session is created.

A record is interpreted using fields GP_SATZART and JPARVW.

The following actions are possible:

Record type	Role (JPARVW)	Action
'ND'		(Optional) definition of
		NO DATA indicator to
		check value entered
'10'	GP,WE,RE,...	Define purchase address
		for subsequent action
		(record types '12' or '13')
		(reference record)
'11'	WE,RE,...	Create an additional
		address
'12'	GP,WE,RE,...	Relocation
'13'	GP,WE,RE,...	Correct address from
		a date
'14'	GP,WE,RE,...	Delete address
'15'	GP,WE,RE,...	Correct address
The '...': stands for all roles in table TJG66.

A record of record type 'ND' must be the first record in the inbound file so that the NO DATA indicator specified on the selection screen is checked. Later records are ignored.

Records that are not imported as a batch input session are written to a separate data file. For example, it is not possible to create a session when a role does not exist, since it is not possible to create a process flow.

Available data structures:

- Record type 'ND':
RJGAU_ND.

- Record types '10', '11', '12', '13', and '14':
RJGAU or RJGAU_GP; however, fields without an address reference are ignored (for example, field JKTOKD (= account group) is irrelevant here).

Notes on Reference Address

When creating or changing an address, you must specify the roles and time slices to which the action applies. There are two possibilities:

In the case of a record not preceded by a reference record, the role is combined with the start of validity (WDAT1) as a reference to the existing addresses. This is only unique if there is only one address history for this role. This is always the case for the role 'GP'. There can be more than one address history for the other roles. Where this is the case, the change affects the first address history.
If a record is preceded by a reference record, this reference record defines the address that is to be changed. This is defined using all the fields in structure RJGAU_ADR (role, validity period, address data).

The reference address (record type 10) can be checked when the batch input session is created. However, this check can only be carried out properly if the reference address already exists in the system at the time at which the batch input session is created. This is for example not the case if it is to be created in this session.

Further notes:

The reference record that defines an address to be changed is not required before every change record. The following rules apply:

If an address is to be changed for a 'GP' role, a preceding reference record is not required.

If you want to change an address for any of the roles 'WE', 'RE', or 'RG', you must ensure that the address to be changed is unique. The following scenarios are possible:
- There is only one address history for the role to be changed. In this case, the above note on role 'GP' applies.
- There are several address histories for the role to be changed.
If there is no preceding reference record, the first address <itf:br/> history for the role is modified. If you do not want this to <itf:br/> happen, there must be a preceding reference record. If the only <itf:br/> entries apart from the business partner number ('GPNR') are the <itf:br/> role ('JPARVW') and the start ('WDAT1') and end of validity <itf:br/> ('WDAT2'), only this data is used to determine the address history <itf:br/> that is to be changed. If further data is entered (which must be <itf:br/> the case if there are addresses with the same start and end dates <itf:br/> in different address histories), these are also used to determine <itf:br/> the address for change.

Upper and lower case should be taken into account for all 'name fields'.

Dates must be entered in the form YYYYMMDD.

It is easiest if you generate a structure description in a higher programming language using the function for generating a table description directly from the system (menu path: Tools -> ABAP Workbench -> Dictionary, and then Environment -> Generate Table Description).

Data Structures

Notes

You imported business partners and now want to import their address histories. If a reference record is required in order to do this, it must correspond exactly to the existing data in the system. However, if the address was corrected when the first import took place, this is only possible with difficulty.

You can use the function module ISP_ADDRESSES_READ to determine the address of a business partner for a particular role and within a particular period. The reference record can be set up from the data determined.

PERFORM Short Reference BAL Application Log Documentation
This documentation is copyright by SAP AG.

Length: 8355 Date: 20240531 Time: 114912 sap01-206 ( 113 ms )

Ansicht Dokumentation