Logon to the CRM system and use the transaction /nasci
.
Frontend for BDoc Generator
screen gets invoked on the desktop.
Enter a name in the BDoc' transaction name
list box and click on the Save
symbol.
Ensure that no duplicate entries are made.
Copy functionality is provided to copy the necessary BDoc‘. Multiple deletion for BDoc‘ is provided ensuring that all details of the BDoc‘ are deleted.
Choose a BDoc‘ and click on the
symbol to map BDoc‘ to a BDoc type.The subsequent screen gets invoked on the desktop.
Enter a short name for the BDoc' transaction in BDoc' trans short name
edit box.
Enter the BDoc with which you want to map the BDoc' in BDoc transaction name
edit box.
Note
Edit fields 'Input func module name'
and 'Output func module name'
have to be ignored for this version.
Enter the mapping name for these transactions in Map Name
edit box.
This map name has to correspond to the map name defined in Structure Mapper. BDoc Generator function applies this mapping for the BDoc' defined in the mapping tool.
The map name in the Structure Mapper has to be defined only for the particular BDoc type to which BDoc’ is mapped. In the F4 help provided, only those map names with consistency in BDoc types are shown (i.e. if map includes two or more BDoc types, such maps are not meant for use by the ASCII ADAPTER).
Note
Structure Mapper details have to be defined and generated before defining details for BDoc’ Generator.
Click on the Save
symbol to save the settings.
A BDoc' is created.
Note
Note that the SMO7_ASCMP table is used to map a BDoc' to a BDoc type.
BDoc’->BDoc screen specifies the mandatory fields to be entered.
F4 help is provided for BDoc transaction name and Mapname.