SAP ABAP Data Element ADDIS_IDOCFB (Additionals: IDoc status in the sub-system)

Hierarchy

☛ BBPCRM (Software Component) BBPCRM
   ⤷ LO-ADM (Application Component) Additionals Management
     ⤷ WTAD (Package) IS-R: Additionals

Basic Data

Data Element	ADDIS_IDOCFB
Short Description	Additionals: IDoc status in the sub-system

Data Type

Category of Dictionary Type	D	Domain
Type of Object Referenced		No Information
Domain / Name of Reference Type	ADDIS_2
Data Type	CHAR	Character String
Length	1
Decimal Places	0
Output Length	1
Value Table

Further Characteristics

Search Help: Name
Search Help: Parameters
Parameter ID
Default Component name
Change document	☐
No Input History	☐
Basic direction is set to LTR	☐
No BIDI Filtering	☐

Field Label

	Length	Field Label
Short	10	IDoc
Medium	20	Sub-sys. IDoc status
Long	23	Sub-system IDoc status
Heading	25	Sub-system IDoc status

Documentation

Definition

Processing status for an IDoc with data for additionals using a subsystem.

Use

Additionals such as price tickets, posters or flyers are not printed via the SAP system. Instead, subsystems fulfil this function.

Subsystems can confirm the IDoc processing status to your SAP system. In doing so, you can follow the processing of your additional from when the IDoc is generated through to when it is printed.

The status is updated by the subsystem using the ChangeStatus method from the "SalesAdditionalsReq" business object. The following characteristics are possible for the status:

• Blank character
  Updating the status using subsystems is irrelevant.
• 1
  The status is not yet updated by the system.
• 2
  The subsystem has partly processed the additionals IDoc.
• 3
  The subsystem has successfully processed the IDoc.

Notes

The relevant indicator for the merchandise category for your additional must be activated before the status of a subsystem can be updated in Customizing.

History

Last changed by/on	SAP	19990504
SAP Release Created in