SAP ABAP Data Element J_1BNFERFCCALL (Control Doc. No. and RFC Execution to Messaging System)
Hierarchy
☛
BBPCRM (Software Component) BBPCRM
⤷ CRM-LOC-BR (Application Component) Brazil
⤷ J1BA (Package) Localization Brazil
⤷ CRM-LOC-BR (Application Component) Brazil
⤷ J1BA (Package) Localization Brazil
Basic Data
Data Element | J_1BNFERFCCALL |
Short Description | Control Doc. No. and RFC Execution to Messaging System |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | J_1BNFERFCCALL | |
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 | RFC Exec. |
Medium | 15 | RFC Execution |
Long | 20 | RFC Execution |
Heading | 9 | RFC Exec. |
Documentation
Definition
Controls how the numbering and the RFC execution for creation of the XML file is executed in the SAP ERP backend.
Use
Possible values for this field include the following:
SPACE - RFC execution and database update in the same LUW (default)
1 - Numbering & RFC triggered via the Monitor Report (J1BNFE)
2 - Numbering in Monitor Report - RFC via batch report
3 - Numbering & RFC triggered via Batch report (J_BNFECALLRFC)
Before the availability of this field, the numbering and RFC execution was in the same LUW as the database update of the document.
Dependencies
Example
History
Last changed by/on | SAP | 20130529 |
SAP Release Created in | 605 |