SAP FUD_DOCDATA_TO_CONTEXT Function Module for Mapping Document Data to BRFplus Context

Search SAP Function Modules

FUD_DOCDATA_TO_CONTEXT is a standard fud docdata to context SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Mapping Document Data to BRFplus Context processing and below is the pattern details for this FM, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.

See here to view full function module documentation and code listing for fud docdata to context FM, simply by entering the name FUD_DOCDATA_TO_CONTEXT into the relevant SAP transaction such as SE37 or SE38.

Function Group: FIN_UI_DECO_BRFPLUS
Program Name: SAPLFIN_UI_DECO_BRFPLUS
Main Program: SAPLFIN_UI_DECO_BRFPLUS
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FUD_DOCDATA_TO_CONTEXT pattern details

In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.

CALL FUNCTION 'FUD_DOCDATA_TO_CONTEXT'"Mapping Document Data to BRFplus Context
  EXPORTING
   IV_APP_ID =  "FDT: Universal Unique Identifier
   IV_FUNCTION_ID =  "FDT: Universal Unique Identifier
   IV_TIMESTAMP =  "UTC Time Stamp in Short Form (YYYYMMDDhhmmss)
   IV_TRACE_GENERATION =  "
   IS_HEADER =  "Accounting Document Header
   IT_ITEM =  "Table Type for BSEG

 IMPORTING
   EV_ERROR =  "
   ET_NAME_VALUE =  "

.

IMPORTING Parameters details for FUD_DOCDATA_TO_CONTEXT

IV_APP_ID - FDT: Universal Unique Identifier

Data type: FDT_UUID
Optional: No
Call by Reference: Yes

IV_FUNCTION_ID - FDT: Universal Unique Identifier

Data type: FDT_UUID
Optional: No
Call by Reference: Yes

IV_TIMESTAMP - UTC Time Stamp in Short Form (YYYYMMDDhhmmss)

Data type: TIMESTAMP
Optional: No
Call by Reference: Yes

IV_TRACE_GENERATION -

Data type: ABAP_BOOL
Optional: No
Call by Reference: Yes

IS_HEADER - Accounting Document Header

Data type: BKPF
Optional: No
Call by Reference: Yes

IT_ITEM - Table Type for BSEG

Data type: BSEG_T
Optional: No
Call by Reference: Yes

EXPORTING Parameters details for FUD_DOCDATA_TO_CONTEXT

EV_ERROR -

Data type: ABAP_BOOL
Optional: No
Call by Reference: Yes

ET_NAME_VALUE -

Data type: ABAP_PARMBIND_TAB
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for FUD_DOCDATA_TO_CONTEXT Function Module

The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than the latest in-line data DECLARATION SYNTAX but I have included an ABAP code snippet at the end to show how declarations would look using the newer method of declaring data variables on the fly. This will allow you to compare and fully understand the new inline method. Please note some of the newer syntax such as the @DATA is not available until a later 4.70 service pack (SP8), which i why i have stuck to the origianl for this example.

ABAP code using 7.40 inline data declarations to call FM FUD_DOCDATA_TO_CONTEXT

The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.

Search for further information about these or an SAP related objects