Ansicht
Dokumentation
RJKRGOLIVE - IS-M/SD: Order Data Transfer (Liability Account and Dep.Data)
ROGBILLS - Synchronize billing plans ABAP Short ReferenceThis documentation is copyright by SAP AG.
Description
Certain pieces of legacy data must be transported into the system in a separate transfer run during legacy data transfer for renewal-controlled subscriptions and subscriptions with liability accounts.
This data must be imported into the system immediately before going live.
After data transfer, IS-M is the leading system (the date of going live must be set) and contains the latest status of the legacy system.
Changes to order data can now only take place in IS-M. Transferring order data from the legacy system for a second time can lead to inconsistent data.
If unexpected problems arise during data transfer, the data already imported into the system can be deleted again using report RJKRRESET.
The following structures are used for transfer, and they must display the appropriate record type as an identifier:
| Rec.type | Structure | Meaning | |
|---|---|---|---|
| '07' | RJKIF_S_ITEMREMIND | Data for monitoring control | |
| - required for renewal-controlled orders with an | |||
| open monitoring cycle | |||
| - allowed for renewal-controlled orders with a | |||
| closed monitoring cycle (if this data is not made | |||
| available, the required information is generated | |||
| internally. However, in this case, there is no | |||
| reference to the accepted offer) | |||
| - not allowed otherwise | |||
| '08' | RJKIF_S_ITEMACC | Data on liability account | |
| - required for orders with a liability account | |||
| - not allowed for orders without a liability account | |||
| '10' | RJKIF_S_ITEMACCFIZUO | Data on incoming payments | |
| - allowed for orders with a monetary liability account | |||
| - not allowed otherwise |
Records in the dataset to be imported that follow on from each other and have the same reference number refer to one order item and are processed together.
You do not need to specify an order number: however, if you do specify one, it must correspond to the order number determined from the reference document number.
Meaning of individual fields:
- RJKIF_S_ITEMREMIND
- REMSTEPTYP: used to determine the step in the monitoring procedure. All values that can only occur once in a procedure are allowed. These are all step types with an assigned activity (e.g. create offer, terminate, ...)
- REMSTATUS: monitoring status. The following values are allowed:
- 01: Cycle created
- 02: Offer created
- 05: Item suspended
- 10: Item terminated
- 11: Offer accepted (cycle completed)
- 12: Item completed (cycle completed)
rdisp/max_wprun_time - Maximum work process run time General Data in Customer Master
This documentation is copyright by SAP AG.
Length: 3933 Date: 20240531 Time: 114909 sap01-206 ( 37 ms )
