SAP POS_SA_RELATE_DOCUMENTS_UPDATE Function Module for NOTRANSL: Verbucher-Version von POS_SA_RELATE_DOCUMENTS, Doku siehe dort
POS_SA_RELATE_DOCUMENTS_UPDATE is a standard pos sa relate documents update SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Verbucher-Version von POS_SA_RELATE_DOCUMENTS, Doku siehe dort 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 pos sa relate documents update FM, simply by entering the name POS_SA_RELATE_DOCUMENTS_UPDATE into the relevant SAP transaction such as SE37 or SE38.
Function Group: WPSA
Program Name: SAPLWPSA
Main Program: SAPLWPSA
Appliation area: W
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update: 1

Function POS_SA_RELATE_DOCUMENTS_UPDATE 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 'POS_SA_RELATE_DOCUMENTS_UPDATE'"NOTRANSL: Verbucher-Version von POS_SA_RELATE_DOCUMENTS, Doku siehe dort.
EXPORTING
DOCNUM = "IDoc Number
SEGNUM = "Number of SAP segment
SEGNUM_END = "Number of SAP segment
* ATTR = "DE-EN-LANG-SWITCH-NO-TRANSLATION
UPLOADNR = "DE-EN-LANG-SWITCH-NO-TRANSLATION
UPLOADDATE = "ABAP System Field: Current Date of Application Server
MESTYP = "Message Type
SNDPRN = "Partner Number of Sender
TABLES
FOLDOC = "DE-EN-LANG-SWITCH-NO-TRANSLATION
Customer Function user exits
Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.EXIT_SAPLWPSA_001 Change the Control for Document Links and POS Monitoring
IMPORTING Parameters details for POS_SA_RELATE_DOCUMENTS_UPDATE
DOCNUM - IDoc Number
Data type: EDIDC-DOCNUMOptional: No
Call by Reference: No ( called with pass by value option)
SEGNUM - Number of SAP segment
Data type: EDIDS-SEGNUMOptional: No
Call by Reference: No ( called with pass by value option)
SEGNUM_END - Number of SAP segment
Data type: EDIDS-SEGNUMOptional: No
Call by Reference: No ( called with pass by value option)
ATTR - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type: WPUSA_EXTDOC_ATTROptional: Yes
Call by Reference: No ( called with pass by value option)
UPLOADNR - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type: WPUSA_UPLOADNROptional: No
Call by Reference: No ( called with pass by value option)
UPLOADDATE - ABAP System Field: Current Date of Application Server
Data type: SY-DATUMOptional: No
Call by Reference: No ( called with pass by value option)
MESTYP - Message Type
Data type: EDIDC-MESTYPOptional: No
Call by Reference: No ( called with pass by value option)
SNDPRN - Partner Number of Sender
Data type: EDIDC-SNDPRNOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for POS_SA_RELATE_DOCUMENTS_UPDATE
FOLDOC - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type: WPUSA_T_FOLDOCOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for POS_SA_RELATE_DOCUMENTS_UPDATE 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.| DATA: | ||||
| lv_docnum | TYPE EDIDC-DOCNUM, " | |||
| lt_foldoc | TYPE STANDARD TABLE OF WPUSA_T_FOLDOC, " | |||
| lv_segnum | TYPE EDIDS-SEGNUM, " | |||
| lv_segnum_end | TYPE EDIDS-SEGNUM, " | |||
| lv_attr | TYPE WPUSA_EXTDOC_ATTR, " | |||
| lv_uploadnr | TYPE WPUSA_UPLOADNR, " | |||
| lv_uploaddate | TYPE SY-DATUM, " | |||
| lv_mestyp | TYPE EDIDC-MESTYP, " | |||
| lv_sndprn | TYPE EDIDC-SNDPRN. " |
|   CALL FUNCTION 'POS_SA_RELATE_DOCUMENTS_UPDATE' "NOTRANSL: Verbucher-Version von POS_SA_RELATE_DOCUMENTS, Doku siehe dort |
| EXPORTING | ||
| DOCNUM | = lv_docnum | |
| SEGNUM | = lv_segnum | |
| SEGNUM_END | = lv_segnum_end | |
| ATTR | = lv_attr | |
| UPLOADNR | = lv_uploadnr | |
| UPLOADDATE | = lv_uploaddate | |
| MESTYP | = lv_mestyp | |
| SNDPRN | = lv_sndprn | |
| TABLES | ||
| FOLDOC | = lt_foldoc | |
| . " POS_SA_RELATE_DOCUMENTS_UPDATE | ||
ABAP code using 7.40 inline data declarations to call FM POS_SA_RELATE_DOCUMENTS_UPDATE
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.| "SELECT single DOCNUM FROM EDIDC INTO @DATA(ld_docnum). | ||||
| "SELECT single SEGNUM FROM EDIDS INTO @DATA(ld_segnum). | ||||
| "SELECT single SEGNUM FROM EDIDS INTO @DATA(ld_segnum_end). | ||||
| "SELECT single DATUM FROM SY INTO @DATA(ld_uploaddate). | ||||
| "SELECT single MESTYP FROM EDIDC INTO @DATA(ld_mestyp). | ||||
| "SELECT single SNDPRN FROM EDIDC INTO @DATA(ld_sndprn). | ||||
Search for further information about these or an SAP related objects