SAP P_ORDER_ARCHIVE_ENTRY Function Module for NOTRANSL: Auftragsreorg: Einstieg
P_ORDER_ARCHIVE_ENTRY is a standard p order archive entry 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: Auftragsreorg: Einstieg 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 p order archive entry FM, simply by entering the name P_ORDER_ARCHIVE_ENTRY into the relevant SAP transaction such as SE37 or SE38.
Function Group: COA0
Program Name: SAPLCOA0
Main Program: SAPLCOA0
Appliation area: C
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function P_ORDER_ARCHIVE_ENTRY 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 'P_ORDER_ARCHIVE_ENTRY'"NOTRANSL: Auftragsreorg: Einstieg.
EXPORTING
ORDER_TYPE = "Order category
* I_SNAP = "ILM Snapshot Action
* I_DEST = "ILM Data Destruction Action
TEST_ARC = "Selection indicator
DELETE = "Selection indicator
NOTICE = "Archiving Session Note
ARCHIVE_OBJECT = "Archiving Object
* ORDER_PACKAGE_SIZE = 10 "Archiving: Block size for database access
* CREATE_NEW_FILE = 'X' "Selection indicator
* OBJECTS_TO_DELETE = "Object selection for object overviews
* I_AR_ILM = "ILM Archiving Action
TABLES
ORDERS = "Structure of Transfer Table for PRE_READ of Orders
* ERRORS = "Message structure of PPSFCACT
EXCEPTIONS
ARCHIVING_ERROR = 1
IMPORTING Parameters details for P_ORDER_ARCHIVE_ENTRY
ORDER_TYPE - Order category
Data type: AUFK-AUTYPOptional: No
Call by Reference: No ( called with pass by value option)
I_SNAP - ILM Snapshot Action
Data type: ILM_WRITE_SNAPOptional: Yes
Call by Reference: No ( called with pass by value option)
I_DEST - ILM Data Destruction Action
Data type: ILM_WRITE_DESTOptional: Yes
Call by Reference: No ( called with pass by value option)
TEST_ARC - Selection indicator
Data type: RC27X-FLG_SELOptional: No
Call by Reference: No ( called with pass by value option)
DELETE - Selection indicator
Data type: RC27X-FLG_SELOptional: No
Call by Reference: No ( called with pass by value option)
NOTICE - Archiving Session Note
Data type: ADMI_RUN-COMMENTSOptional: No
Call by Reference: No ( called with pass by value option)
ARCHIVE_OBJECT - Archiving Object
Data type: ARCH_OBJ-OBJECTOptional: No
Call by Reference: No ( called with pass by value option)
ORDER_PACKAGE_SIZE - Archiving: Block size for database access
Data type: COARCH-DBNUMDefault: 10
Optional: Yes
Call by Reference: No ( called with pass by value option)
CREATE_NEW_FILE - Selection indicator
Data type: RC27X-FLG_SELDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
OBJECTS_TO_DELETE - Object selection for object overviews
Data type: TCA11Optional: Yes
Call by Reference: No ( called with pass by value option)
I_AR_ILM - ILM Archiving Action
Data type: ILM_WRITE_ARCHOptional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for P_ORDER_ARCHIVE_ENTRY
ORDERS - Structure of Transfer Table for PRE_READ of Orders
Data type: ORD_PREOptional: No
Call by Reference: No ( called with pass by value option)
ERRORS - Message structure of PPSFCACT
Data type: COACTMSGOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
ARCHIVING_ERROR -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for P_ORDER_ARCHIVE_ENTRY 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: | ||||
| lt_orders | TYPE STANDARD TABLE OF ORD_PRE, " | |||
| lv_order_type | TYPE AUFK-AUTYP, " | |||
| lv_archiving_error | TYPE AUFK, " | |||
| lv_i_snap | TYPE ILM_WRITE_SNAP, " | |||
| lv_i_dest | TYPE ILM_WRITE_DEST, " | |||
| lt_errors | TYPE STANDARD TABLE OF COACTMSG, " | |||
| lv_test_arc | TYPE RC27X-FLG_SEL, " | |||
| lv_delete | TYPE RC27X-FLG_SEL, " | |||
| lv_notice | TYPE ADMI_RUN-COMMENTS, " | |||
| lv_archive_object | TYPE ARCH_OBJ-OBJECT, " | |||
| lv_order_package_size | TYPE COARCH-DBNUM, " 10 | |||
| lv_create_new_file | TYPE RC27X-FLG_SEL, " 'X' | |||
| lv_objects_to_delete | TYPE TCA11, " | |||
| lv_i_ar_ilm | TYPE ILM_WRITE_ARCH. " |
|   CALL FUNCTION 'P_ORDER_ARCHIVE_ENTRY' "NOTRANSL: Auftragsreorg: Einstieg |
| EXPORTING | ||
| ORDER_TYPE | = lv_order_type | |
| I_SNAP | = lv_i_snap | |
| I_DEST | = lv_i_dest | |
| TEST_ARC | = lv_test_arc | |
| DELETE | = lv_delete | |
| NOTICE | = lv_notice | |
| ARCHIVE_OBJECT | = lv_archive_object | |
| ORDER_PACKAGE_SIZE | = lv_order_package_size | |
| CREATE_NEW_FILE | = lv_create_new_file | |
| OBJECTS_TO_DELETE | = lv_objects_to_delete | |
| I_AR_ILM | = lv_i_ar_ilm | |
| TABLES | ||
| ORDERS | = lt_orders | |
| ERRORS | = lt_errors | |
| EXCEPTIONS | ||
| ARCHIVING_ERROR = 1 | ||
| . " P_ORDER_ARCHIVE_ENTRY | ||
ABAP code using 7.40 inline data declarations to call FM P_ORDER_ARCHIVE_ENTRY
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 AUTYP FROM AUFK INTO @DATA(ld_order_type). | ||||
| "SELECT single FLG_SEL FROM RC27X INTO @DATA(ld_test_arc). | ||||
| "SELECT single FLG_SEL FROM RC27X INTO @DATA(ld_delete). | ||||
| "SELECT single COMMENTS FROM ADMI_RUN INTO @DATA(ld_notice). | ||||
| "SELECT single OBJECT FROM ARCH_OBJ INTO @DATA(ld_archive_object). | ||||
| "SELECT single DBNUM FROM COARCH INTO @DATA(ld_order_package_size). | ||||
| DATA(ld_order_package_size) | = 10. | |||
| "SELECT single FLG_SEL FROM RC27X INTO @DATA(ld_create_new_file). | ||||
| DATA(ld_create_new_file) | = 'X'. | |||
Search for further information about these or an SAP related objects