SAP UPB_PM_ASSIGNS_CREATE Function Module for Create new object in Framework - common pop-up for create and copy
UPB_PM_ASSIGNS_CREATE is a standard upb pm assigns create SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Create new object in Framework - common pop-up for create and copy 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 upb pm assigns create FM, simply by entering the name UPB_PM_ASSIGNS_CREATE into the relevant SAP transaction such as SE37 or SE38.
Function Group: UPB_PM_DOC
Program Name: SAPLUPB_PM_DOC
Main Program: SAPLUPB_PM_DOC
Appliation area: R
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function UPB_PM_ASSIGNS_CREATE 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 'UPB_PM_ASSIGNS_CREATE'"Create new object in Framework - common pop-up for create and copy.
EXPORTING
* I_AREA = "Planning Area
* I_PLEVEL = "Planning Level
* I_PACKAGE = "Planning Package
* I_METHOD = "Planning Method
* I_PARAM = "Planning Parameters
IT_PLEVELC = "Characteristics
IT_PACKAGE_DOC_SEL = "Characteristic Selection
IT_KYF = "Key Figures
I_TEXT_DOCS_ALLOWED = "Planning Folders: Status
IMPORTING
E_TECH_NAME = "Title for BDS
E_CANCEL = "OK or Cancel
E_DOCTYPE = "OLE document type
CHANGING
* XT_CHA_SEL = "Single-Character Flag
IMPORTING Parameters details for UPB_PM_ASSIGNS_CREATE
I_AREA - Planning Area
Data type: UPC_Y_AREAOptional: Yes
Call by Reference: No ( called with pass by value option)
I_PLEVEL - Planning Level
Data type: UPC_Y_PLEVELOptional: Yes
Call by Reference: No ( called with pass by value option)
I_PACKAGE - Planning Package
Data type: UPC_Y_PACKAGEOptional: Yes
Call by Reference: No ( called with pass by value option)
I_METHOD - Planning Method
Data type: UPC_Y_METHODOptional: Yes
Call by Reference: No ( called with pass by value option)
I_PARAM - Planning Parameters
Data type: UPC_Y_PARAMOptional: Yes
Call by Reference: No ( called with pass by value option)
IT_PLEVELC - Characteristics
Data type: UPC_YTO_CHAOptional: No
Call by Reference: Yes
IT_PACKAGE_DOC_SEL - Characteristic Selection
Data type: UPC_YTO_CHASELOptional: No
Call by Reference: Yes
IT_KYF - Key Figures
Data type: UPC_YTO_KYFOptional: No
Call by Reference: Yes
I_TEXT_DOCS_ALLOWED - Planning Folders: Status
Data type: UPB_Y_PM_FLAGOptional: No
Call by Reference: Yes
EXPORTING Parameters details for UPB_PM_ASSIGNS_CREATE
E_TECH_NAME - Title for BDS
Data type: UPC_YS_DOCUMENT-DOC_TITLEOptional: No
Call by Reference: Yes
E_CANCEL - OK or Cancel
Data type: CHAR1Optional: No
Call by Reference: Yes
E_DOCTYPE - OLE document type
Data type: BDS_MIMETPOptional: No
Call by Reference: Yes
CHANGING Parameters details for UPB_PM_ASSIGNS_CREATE
XT_CHA_SEL - Single-Character Flag
Data type: UPC_YTO_CHACOMBOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for UPB_PM_ASSIGNS_CREATE 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_i_area | TYPE UPC_Y_AREA, " | |||
| lv_xt_cha_sel | TYPE UPC_YTO_CHACOMB, " | |||
| lv_e_tech_name | TYPE UPC_YS_DOCUMENT-DOC_TITLE, " | |||
| lv_e_cancel | TYPE CHAR1, " | |||
| lv_i_plevel | TYPE UPC_Y_PLEVEL, " | |||
| lv_e_doctype | TYPE BDS_MIMETP, " | |||
| lv_i_package | TYPE UPC_Y_PACKAGE, " | |||
| lv_i_method | TYPE UPC_Y_METHOD, " | |||
| lv_i_param | TYPE UPC_Y_PARAM, " | |||
| lv_it_plevelc | TYPE UPC_YTO_CHA, " | |||
| lv_it_package_doc_sel | TYPE UPC_YTO_CHASEL, " | |||
| lv_it_kyf | TYPE UPC_YTO_KYF, " | |||
| lv_i_text_docs_allowed | TYPE UPB_Y_PM_FLAG. " |
|   CALL FUNCTION 'UPB_PM_ASSIGNS_CREATE' "Create new object in Framework - common pop-up for create and copy |
| EXPORTING | ||
| I_AREA | = lv_i_area | |
| I_PLEVEL | = lv_i_plevel | |
| I_PACKAGE | = lv_i_package | |
| I_METHOD | = lv_i_method | |
| I_PARAM | = lv_i_param | |
| IT_PLEVELC | = lv_it_plevelc | |
| IT_PACKAGE_DOC_SEL | = lv_it_package_doc_sel | |
| IT_KYF | = lv_it_kyf | |
| I_TEXT_DOCS_ALLOWED | = lv_i_text_docs_allowed | |
| IMPORTING | ||
| E_TECH_NAME | = lv_e_tech_name | |
| E_CANCEL | = lv_e_cancel | |
| E_DOCTYPE | = lv_e_doctype | |
| CHANGING | ||
| XT_CHA_SEL | = lv_xt_cha_sel | |
| . " UPB_PM_ASSIGNS_CREATE | ||
ABAP code using 7.40 inline data declarations to call FM UPB_PM_ASSIGNS_CREATE
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 DOC_TITLE FROM UPC_YS_DOCUMENT INTO @DATA(ld_e_tech_name). | ||||
Search for further information about these or an SAP related objects