SAP PS_ORDER_ARCHIVE_OBJECT Function Module for NOTRANSL: Archivieren Projekt









PS_ORDER_ARCHIVE_OBJECT is a standard ps order archive object 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: Archivieren Projekt 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 ps order archive object FM, simply by entering the name PS_ORDER_ARCHIVE_OBJECT into the relevant SAP transaction such as SE37 or SE38.

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



Function PS_ORDER_ARCHIVE_OBJECT 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 'PS_ORDER_ARCHIVE_OBJECT'"NOTRANSL: Archivieren Projekt
EXPORTING
ARCHIVE_HANDLE = "ABAP System Field: Row Index of Internal Tables
* OBJECT_DELETE_FLAG = ' ' "

TABLES
* T_ORDER = "List of order numbers
* T_SALES_ORDER = "List of SD order numbers
* T_PLAN_ORDER = "Keys of planned orders (parameter of FuGr M61E)
* T_SALES_POSITION = "List of sales order items
* T_MAINT_ORDER = "List of order numbers

EXCEPTIONS
WRONG_ACCESS_TO_ARCHIVE = 1 NOT_FOUND = 2
.



IMPORTING Parameters details for PS_ORDER_ARCHIVE_OBJECT

ARCHIVE_HANDLE - ABAP System Field: Row Index of Internal Tables

Data type: SY-TABIX
Optional: No
Call by Reference: No ( called with pass by value option)

OBJECT_DELETE_FLAG -

Data type:
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for PS_ORDER_ARCHIVE_OBJECT

T_ORDER - List of order numbers

Data type: RCJ_AUFNR
Optional: Yes
Call by Reference: No ( called with pass by value option)

T_SALES_ORDER - List of SD order numbers

Data type: RCJ_VBELN
Optional: Yes
Call by Reference: No ( called with pass by value option)

T_PLAN_ORDER - Keys of planned orders (parameter of FuGr M61E)

Data type: PLAF_PLNUM
Optional: Yes
Call by Reference: No ( called with pass by value option)

T_SALES_POSITION - List of sales order items

Data type: RCJ_VPOSNR
Optional: Yes
Call by Reference: No ( called with pass by value option)

T_MAINT_ORDER - List of order numbers

Data type: RCJ_AUFNR
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

WRONG_ACCESS_TO_ARCHIVE - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

NOT_FOUND -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for PS_ORDER_ARCHIVE_OBJECT 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_t_order  TYPE STANDARD TABLE OF RCJ_AUFNR, "   
lv_archive_handle  TYPE SY-TABIX, "   
lv_wrong_access_to_archive  TYPE SY, "   
lv_not_found  TYPE SY, "   
lt_t_sales_order  TYPE STANDARD TABLE OF RCJ_VBELN, "   
lv_object_delete_flag  TYPE RCJ_VBELN, "   SPACE
lt_t_plan_order  TYPE STANDARD TABLE OF PLAF_PLNUM, "   
lt_t_sales_position  TYPE STANDARD TABLE OF RCJ_VPOSNR, "   
lt_t_maint_order  TYPE STANDARD TABLE OF RCJ_AUFNR. "   

  CALL FUNCTION 'PS_ORDER_ARCHIVE_OBJECT'  "NOTRANSL: Archivieren Projekt
    EXPORTING
         ARCHIVE_HANDLE = lv_archive_handle
         OBJECT_DELETE_FLAG = lv_object_delete_flag
    TABLES
         T_ORDER = lt_t_order
         T_SALES_ORDER = lt_t_sales_order
         T_PLAN_ORDER = lt_t_plan_order
         T_SALES_POSITION = lt_t_sales_position
         T_MAINT_ORDER = lt_t_maint_order
    EXCEPTIONS
        WRONG_ACCESS_TO_ARCHIVE = 1
        NOT_FOUND = 2
. " PS_ORDER_ARCHIVE_OBJECT




ABAP code using 7.40 inline data declarations to call FM PS_ORDER_ARCHIVE_OBJECT

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 TABIX FROM SY INTO @DATA(ld_archive_handle).
 
 
 
 
DATA(ld_object_delete_flag) = ' '.
 
 
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!