/
IDoc Management in VSS-DSW

IDoc Management in VSS-DSW

VSS uses IDoc when communicating with DSW. These are inbound and outbound IDocs corresponding to the real communication between the two applications. IDocs mechanism is utilized to generate the trace information - network calls can be traced by means of IDocs.

The following are transactions prepared to distribute the business objects to DSW.

Distribution

Sending VSS objects in scope of the VSS-DSW.

No.

Description

Transaction Code

No.

Description

Transaction Code

1.

Distribution Item Data

/DBE/ODL_ITEM_DIST

2.

Distribution Vehicle Reservation

/DBE/ODL_VEH_RSV_DIS

3.

Distribution Vehicle

/DBE/ODL_VEH_DISTRIB

4.

Distribution BP Data

/DBE/ODL_BP_DISTRIBU

5.

Distribution Vehicle Assignment to Sales Order

/DBE/ODL_VASSIGN_DIS

6.

Distribute Status of orders to DSW

/DBE/ODL_ORD_ST_DIST

 

Interface / IDoc Monitor

Monitoring of inbound and outbound message for purpose of trouble-shooting or re-processing. Transaction code: /DBE/IFM

No.

Direction

IDoc Type

Description

No.

Direction

IDoc Type

Description

1.

Outbound

/DBE/ODL_BP_TRACE_OUT

IDoc to trace business partner sent to DSW

2.

Outbound

/DBE/ODL_AITEM_TRACE_OUT

IDoc to trace additional item sent to DSW

3.

Outbound

/DBE/ODL_VEH_TRACE_OUT

IDoc to trace vehicle sent to DSW

4.

Outbound

/DBE/ODL_VEH_RESERV_OUT

IDoc to trace vehicle reservation sent to DSW

5.

Outbound

/DBE/ODL_VASSIGN_TRACE_OUT

IDoc to trace vehicle assignment sent to DSW

6.

Outbound

/DBE/ODL_SYNCH_TRACE_OUT

IDoc to trace Synchronization REST API out

(Update Mapping of Document No.)

7.

Inbound

/DBE/ODL_CUSTOMER_TRACE_IN

IDoc to trace business partner received from DSW

8.

Inbound

/DBE/ODL_PRICING_TRACE_IN

IDoc to trace pricing simulation received from DSW

9.

Inbound

/DBE/ODL_VEH_RESERVATION

IDoc to trace vehicle reservation received from DSW

10.

Inbound

/DBE/ODL_SALES_OFFER_TRACE_IN

IDoc to trace sales offer received from DSW

11.

Inbound

/DBE/ODL_SALES_ORDER_TRACE_IN

IDoc to trace sales order received from DSW

12.

Inbound

/DBE/ODL_SALES_OFFER

IDoc of sales offer ready to be passed to application

13.

Inbound

/DBE/ODL_SALES_ORDER

IDoc of sales order ready to be passed to application

Below is an example of the /DBE/IFM transaction. You can view the request or response file for each generated IDocs according to the IDoc Type.

Maintenance of IDocs for VSS-DSW

In general, IDocs generated in the system needs to be removed periodically as over time, they will consume disk space. How long the IDocs needs to be in the system is the decision of the customer based on various factors for example the criticality of the data and size of database. In any cases, after some times, the IDocs should be removed.

Below are examples of what can be safely removed:

  1. Attachments of the IDocs

  2. Trace IDocs

  3. Processed outbound IDocs with status 18 or 41

  4. Processed inbound IDocs with status 53

VSS provides a transaction (/DBE/ARS_IDOCS_DEL) to remove the IDocs. It can be launched from
the foreground but recommended to be a scheduled job for example, scheduled every night.

 

Related content

IDoc Management in VSS-DSW
IDoc Management in VSS-DSW
More like this
IDoc Management in VSS-DSW
IDoc Management in VSS-DSW
More like this
Monitoring and Tracing
Monitoring and Tracing
More like this
Monitoring and Tracing
Monitoring and Tracing
More like this
Monitoring and Tracing
Monitoring and Tracing
More like this
Reporting - FSM/VSS
Reporting - FSM/VSS
More like this