Cannot use create purchase order in SRM 7.01

Hello,
We are upgrading from SRM 5.0 to SRM 7.0.Classic scenario. In the workset purchasing of the role operational purchasing you can use Create Documents -> purchase order. if I click on it I recieve the following message:
The table does not contain any data
If I then choose start I get the following message:
Transaction type could not be determined; inform system administrator
Can anybody explain to me if is this a purchase order which would be created in SRM ? As we are in the classic scenario we don't want that. If this is a local purchase order how can we create a purchase order in ECC using SRM 7.01
Thanks for your help!
Antoinette

Hi,
In a classic scenario, the SAP SRM system is used mainly to capture procurement requisitions from employees in the form of shopping carts. All other procurement activities take place in the backend materials management system.
So you cannot create po in SRM it will be created in ECC.
Regards,
Goutam Kolluru.

Similar Messages

SRM - Create Purchase order

Hello,
What is the procedure (transactions ??) for create a Purchase Order on SRM ??
Thanks in advance.

Hello,
>
Equipe Archivage wrote:
> I am in SRM System (but not in Portal).
>
> I execute BBPSOCO02 transaction.
>(...)
I guess you run transaction using SAP GUI...
This is not the normal functional way to create purchasing documents, i mean the way used by SRM users.
For this, you must be connected to the SRM server via a web browser using its URL.
Once connected, you will be able to create purchasing documents. Ask to your functional consultant to explain you the whole process.
Regards.
Laurent.

SRM 7.0 Create Purchase Order

Hi SRM Gurus,
We have upgraded from SRM 3.to SRM 7.0.
Our scenario is Extended classic scenario.
click on create Purchase order. Error message is displayed
"table does not contain any data"
I have checked in Define Transaction type for purchase order all the details are there.
Define Transaction type is working for contract,Rfx ,and auction.
It is not working for Purchase order. Which table to check
Can you please give your inputs
Regards
G.Ganesh Kumar

Hi Muthu/Viru
Thanks for the suggestion
I am in SRM 7.0
This issue is resolved and I got another Issue
I have tried to convert the existing SC to a PO . it is not working.
Created a shopping cart ,approved.
Now I converted the SC to P.O. Now all the transaction types were appearing
converted to P.O. but one issue " Please clear the price (or) Set the invoice expected indicator
I could not able to find this in the P.O (SRM 7.0)
Please help
Regards
G.Ganesh Kumar

Problem attempting to create a purchase order via SRM Portal instance.

Unsing SRM7.0 with PPS; When attempting to create a purchase order via the "Create Purchase
Order" button in SRM Portal instance, after select ECPO type; the following message is show in the screen: "Object or set with GUID 00000000000000000000000000000000 does not exist".
Could you please advise what the problem might be and what to do.Thanks, responds would be very appreciated.Kind regards.
Edited by: ital230 on Jun 30, 2010 10:37 AM
Edited by: ital230 on Jun 30, 2010 11:05 AM

Solve!
The problem was the attributes specialy the BSA.
chekout the attribute should be at highest level and in the user not excluded (grayed).
Also
Define Backend System for Product Category: check that the system for category transfer should be from srm to backend:

HOW TO CREATE PURCHASE ORDER USING BAPI

HI FRIENDS,
I HAVE URGENT REQUIREMNT ,TO CREATE PURCHASE ORDER USING BAPI.PLS HELP ON THIS.
UR'S
RAVI

Hi
See the sample code and do accordingly
REPORT zpo_bapi_purchord_tej.
DATA DECLARATIONS *
TYPE-POOLS slis.
TYPES: BEGIN OF ty_table,
v_legacy(8),
vendor TYPE bapimepoheader-vendor,
purch_org TYPE bapimepoheader-purch_org,
pur_group TYPE bapimepoheader-pur_group,
material TYPE bapimepoitem-material,
quantity(13),
delivery_date TYPE bapimeposchedule-delivery_date,
net_price(23),
plant TYPE bapimepoitem-plant,
END OF ty_table.
TYPES: BEGIN OF ty_alv,
v_legs(8),
success(10),
v_legf(8),
END OF ty_alv.
TYPES: BEGIN OF ty_alv1,
v_legf1(8),
v_msg(500),
END OF ty_alv1.
*-----Work area declarations.
DATA: x_table TYPE ty_table,
x_header TYPE bapimepoheader,
x_headerx TYPE bapimepoheaderx,
x_item TYPE bapimepoitem,
x_itemx TYPE bapimepoitemx,
x_sched TYPE bapimeposchedule,
x_schedx TYPE bapimeposchedulx,
x_commatable(255),
x_alv TYPE ty_alv,
x_alv1 TYPE ty_alv1,
x_alv2 TYPE ty_alv1.
*-----Internal table declarations.
DATA: it_table TYPE TABLE OF ty_table,
it_commatable LIKE TABLE OF x_commatable,
it_item TYPE TABLE OF bapimepoitem,
it_itemx TYPE TABLE OF bapimepoitemx,
it_sched TYPE TABLE OF bapimeposchedule,
it_schedx TYPE TABLE OF bapimeposchedulx,
it_alv TYPE TABLE OF ty_alv,
it_alv1 TYPE TABLE OF ty_alv1,
it_alv2 TYPE TABLE OF ty_alv1.
DATA: po_number TYPE bapimepoheader-po_number,
x_return TYPE bapiret2,
it_return TYPE TABLE OF bapiret2,
v_file TYPE string,
v_temp(8),
v_succsount TYPE i VALUE 0,
v_failcount TYPE i VALUE 0,
v_total TYPE i.
DATA: v_temp1(5) TYPE n VALUE 0.
DATA: x_event TYPE slis_t_event,
x_fieldcat TYPE slis_t_fieldcat_alv,
x_list_header TYPE slis_t_listheader,
x_event1 LIKE LINE OF x_event,
x_layout1 TYPE slis_layout_alv,
x_variant1 TYPE disvariant,
x_repid2 LIKE sy-repid.
DATA : it_fieldcat TYPE TABLE OF slis_t_fieldcat_alv.
SELECTION-SCREEN *
SELECTION-SCREEN BEGIN OF BLOCK v_b1 WITH FRAME.
*-----To fetch the flat file.
PARAMETERS: p_file TYPE rlgrap-filename.
SELECTION-SCREEN END OF BLOCK v_b1.
AT SELECTION-SCREEN *
AT SELECTION-SCREEN.
IF p_file IS INITIAL.
MESSAGE text-001 TYPE 'E'.
ENDIF.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_file.
*-----To use F4 help to find file path.
CALL FUNCTION 'F4_FILENAME'
EXPORTING
program_name = syst-cprog
dynpro_number = syst-dynnr
IMPORTING
file_name = p_file.
v_file = p_file.
START-OF-SELECTION *
START-OF-SELECTION.
PERFORM gui_upload.
LOOP AT it_table INTO x_table.
PERFORM header_details.
v_temp = x_table-v_legacy.
LOOP AT it_table INTO x_table WHERE v_legacy = v_temp.
PERFORM lineitem.
PERFORM schedule.
ENDLOOP.
DELETE it_table WHERE v_legacy = v_temp.
PERFORM bapicall.
MOVE po_number TO x_alv-success.
APPEND x_alv TO it_alv.
CLEAR x_alv.
*-----To clear the item details in internal table after the operation for a header.
REFRESH: it_item,
it_itemx,
it_sched,
it_schedx.
CLEAR: v_temp1.
ENDLOOP.
v_total = v_succsount + v_failcount.
PERFORM display_alv.
FORM GUI_UPLOAD *
FORM gui_upload .
CALL FUNCTION 'GUI_UPLOAD'
EXPORTING
filename = v_file
filetype = 'ASC'
TABLES
data_tab = it_commatable
EXCEPTIONS
file_open_error = 1
file_read_error = 2
no_batch = 3
gui_refuse_filetransfer = 4
invalid_type = 5
no_authority = 6
unknown_error = 7
bad_data_format = 8
header_not_allowed = 9
separator_not_allowed = 10
header_too_long = 11
unknown_dp_error = 12
access_denied = 13
dp_out_of_memory = 14
disk_full = 15
dp_timeout = 16
OTHERS = 17
IF sy-subrc = 0.
*-----To fetch the comma seperated flat file into an internal table.
LOOP AT it_commatable INTO x_commatable.
IF x_commatable IS NOT INITIAL.
SPLIT x_commatable AT ',' INTO
x_table-v_legacy
x_table-vendor
x_table-purch_org
x_table-pur_group
x_table-material
x_table-quantity
x_table-delivery_date
x_table-net_price
x_table-plant.
APPEND x_table TO it_table.
ENDIF.
CLEAR x_table.
ENDLOOP.
ENDIF.
ENDFORM. " gui_upload
FORM HEADER_DETAILS *
FORM header_details .
MOVE 'NB' TO x_header-doc_type.
CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
EXPORTING
input = x_table-vendor
IMPORTING
output = x_table-vendor
MOVE x_table-vendor TO x_header-vendor.
MOVE x_table-purch_org TO x_header-purch_org.
MOVE x_table-pur_group TO x_header-pur_group.
x_headerx-doc_type = 'X'.
x_headerx-vendor = 'X'.
x_headerx-purch_org = 'X'.
x_headerx-pur_group = 'X'.
ENDFORM. " header_details
FORM LINEITEM *
FORM lineitem .
v_temp1 = v_temp1 + 10.
CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
EXPORTING
input = v_temp1
IMPORTING
output = v_temp1.
MOVE v_temp1 TO x_item-po_item.
CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
EXPORTING
input = x_table-material
IMPORTING
output = x_table-material.
MOVE x_table-material TO x_item-material.
MOVE x_table-quantity TO x_item-quantity.
MOVE x_table-net_price TO x_item-net_price.
MOVE x_table-plant TO x_item-plant.
x_itemx-po_item = v_temp1.
x_itemx-material = 'X'.
x_itemx-quantity = 'X'.
x_itemx-net_price = 'X'.
x_itemx-plant = 'X'.
APPEND x_item TO it_item.
APPEND x_itemx TO it_itemx.
CLEAR: x_item, x_itemx.
ENDFORM. " lineitem1
FORM SCHEDULE *
FORM schedule .
MOVE x_table-delivery_date TO x_sched-delivery_date.
MOVE v_temp1 TO x_sched-po_item.
x_schedx-delivery_date = 'X'.
x_schedx-po_item = v_temp1.
APPEND x_sched TO it_sched.
APPEND x_schedx TO it_schedx.
CLEAR: x_sched, x_schedx.
ENDFORM. " schedule
FORM BAPICALL *
FORM bapicall .
CALL FUNCTION 'BAPI_PO_CREATE1'
EXPORTING
poheader = x_header
poheaderx = x_headerx
IMPORTING
exppurchaseorder = po_number
TABLES
return = it_return
poitem = it_item
poitemx = it_itemx
poschedule = it_sched
poschedulex = it_schedx.
IF po_number IS NOT INITIAL.
v_succsount = v_succsount + 1.
MOVE x_table-v_legacy TO x_alv-v_legs.
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.
ELSE.
v_failcount = v_failcount + 1.
MOVE x_table-v_legacy TO x_alv-v_legf.
MOVE x_table-v_legacy TO x_alv1-v_legf1.
LOOP AT it_return INTO x_return.
IF x_alv1-v_msg IS INITIAL.
MOVE x_return-message TO x_alv1-v_msg.
ELSE.
CONCATENATE x_alv1-v_msg x_return-message INTO x_alv1-v_msg SEPARATED BY space.
ENDIF.
ENDLOOP.
APPEND x_alv1 TO it_alv1.
CLEAR x_alv1.
ENDIF.
ENDFORM. " bapicall
FORM DISPLAY_ALV *
FORM display_alv .
PERFORM x_list_header.
PERFORM build_fieldcat CHANGING x_fieldcat.
x_repid2 = sy-repid.
x_event1-name = 'TOP_OF_PAGE'.
x_event1-form = 'TOP_OF_PAGE'.
APPEND x_event1 TO x_event.
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
EXPORTING
i_callback_program = x_repid2
is_layout = x_layout1
it_fieldcat = x_fieldcat
i_callback_user_command = 'USER_COMMAND'
i_callback_top_of_page = 'TOP_OF_PAGE'
i_save = 'A'
is_variant = x_variant1
it_events = x_event
TABLES
t_outtab = it_alv
EXCEPTIONS
program_error = 1
OTHERS = 2.
IF sy-subrc <> 0.
MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.
ENDFORM. " display_master_data
FORM USER_COMMAND *
FORM user_command USING ucomm LIKE sy-ucomm selfield
TYPE slis_selfield.
READ TABLE it_alv INTO x_alv INDEX selfield-tabindex.
CLEAR : x_alv2,it_alv2[].
LOOP AT it_alv1 INTO x_alv1 WHERE v_legf1 = x_alv-v_legf.
x_alv2 = x_alv1.
APPEND x_alv2 TO it_alv2 .
ENDLOOP.
DATA : it_fieldcat TYPE slis_t_fieldcat_alv.
DATA : x3_fieldcat LIKE LINE OF it_fieldcat.
CLEAR : x3_fieldcat,it_fieldcat[].
CLEAR x3_fieldcat.
x3_fieldcat-col_pos = '1'.
x3_fieldcat-fieldname = 'V_LEGF1'.
x3_fieldcat-reptext_ddic = text-111.
x3_fieldcat-ref_tabname = 'IT_ALV2'.
APPEND x3_fieldcat TO it_fieldcat.
CLEAR x3_fieldcat.
CLEAR x3_fieldcat.
x3_fieldcat-col_pos = '1'.
x3_fieldcat-fieldname = 'V_MSG'.
x3_fieldcat-reptext_ddic = text-112.
x3_fieldcat-ref_tabname = 'IT_ALV2'.
APPEND x3_fieldcat TO it_fieldcat.
CLEAR x3_fieldcat.
x_layout1-colwidth_optimize = 'X'.
x_layout1-zebra = 'X'.
IF it_alv2[] IS NOT INITIAL.
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
EXPORTING
i_callback_program = x_repid2
is_layout = x_layout1
it_fieldcat = it_fieldcat
i_save = 'A'
i_callback_top_of_page = 'TOP'
is_variant = x_variant1
it_events = x_event
TABLES
t_outtab = it_alv2
EXCEPTIONS
program_error = 1
OTHERS = 2.
ENDIF.
ENDFORM.
FORM USER_COMMAND *
FORM top.
CALL FUNCTION 'REUSE_ALV_COMMENTARY_WRITE'
EXPORTING
it_list_commentary = 'Commentry'.
ENDFORM.
FORM BUILD_FIELDCAT *
FORM build_fieldcat CHANGING et_fieldcat TYPE slis_t_fieldcat_alv.
DATA: x1_fieldcat TYPE slis_fieldcat_alv.
CLEAR x1_fieldcat.
x1_fieldcat-col_pos = '1'.
x1_fieldcat-fieldname = 'V_LEGS'.
x1_fieldcat-reptext_ddic = text-108.
x1_fieldcat-ref_tabname = 'IT_ALV'.
APPEND x1_fieldcat TO et_fieldcat.
CLEAR x1_fieldcat.
x1_fieldcat-col_pos = '2'.
x1_fieldcat-fieldname = 'SUCCESS'.
x1_fieldcat-key = 'X'.
x1_fieldcat-reptext_ddic = text-109.
x1_fieldcat-ref_tabname = 'IT_ALV'.
APPEND x1_fieldcat TO et_fieldcat.
CLEAR x1_fieldcat.
x1_fieldcat-col_pos = '3'.
x1_fieldcat-fieldname = 'V_LEGF'.
x1_fieldcat-key = 'X'.
x1_fieldcat-reptext_ddic = text-110.
x1_fieldcat-ref_tabname = 'IT_ALV'.
APPEND x1_fieldcat TO et_fieldcat.
CLEAR x1_fieldcat.
ENDFORM. " build_fieldcat
FORM BUILD_LIST_HEADER *
FORM x_list_header.
DATA: x_list_header1 TYPE slis_listheader.
*-----List Header: type H
CLEAR x_list_header1 .
x_list_header1-typ = 'H'.
x_list_header1-info = text-105.
APPEND x_list_header1 TO x_list_header.
*-----List Key: type S
x_list_header1-typ = 'S'.
x_list_header1-key = text-106.
x_list_header1-info = v_total.
APPEND x_list_header1 TO x_list_header.
*-----List Key: Type S
CLEAR x_list_header1 .
x_list_header1-typ = 'S'.
x_list_header1-key = text-107.
x_list_header1-info = v_succsount.
APPEND x_list_header1 TO x_list_header.
ENDFORM. " build_list_header
FORM TOP_OF_PAGE *
FORM top_of_page.
CALL FUNCTION 'REUSE_ALV_COMMENTARY_WRITE'
EXPORTING
it_list_commentary = x_list_header.
ENDFORM. " TOP_OF_PAGE
Reward points if useful
Anji

How to create purchase order using SharePoint Custom List

Hi All,
Can you please provide some example or link to create Purchase Order using SharePoint List / SharePoint Designer.
Thanks

Hi,
It would be difficult to achieve what you want with the OOTB features of only one list.
Per my understanding, there would be two main functionalities in the solution you want:
1. Calculate and display the “Balance Qty” dynamically based on the values of “Order Qty” and “Deliver Qty”;
2. Trace the “Deliver Date” and “Deliver Qty” as per “Purchase No”;
As a workaround, I would suggest you create two lists as below:
1. List “Orders”: Saving the upcoming orders per “Purchase No”, one “Order Qty” related to one unique “Purchase No”.
Columns in this list:
Purchase No(Number);
Order Date(Date);
Order Qty(Number);
2. List “Deliveries”: Recording each delivery, one “Deliver Qty” to one unique existing “Purchase No” in list “Orders”.
Columns in this list:
Purchase No(Lookup “Purchase No” in list “Orders”);
Order Date(Additional Lookup column along with “Purchase No”);
Order Qty(Additional Lookup column along with “Purchase No”);
Deliver Date(Date);
Deliver Qty(Number);
Balance Qty(Number);
More information about
Lookup column in SharePoint List:
http://msdn.microsoft.com/en-us/library/office/ff728095(v=office.14).aspx
http://zimmergren.net/technical/sp-2010-how-to-relational-lists-in-sharepoint-2010
In the “Deliveries” list, we can trace each “Deliver Qty” and “Deliver Date” easily by filtering the “Purchase No” column in the list view page.
For the dynamic values in “Balance Qty” column, Event Receiver with custom code would be needed as we will need to query the “Order Qty” in “Orders” list and all the
existing “Deliver Qty” value per “Purchase No” in “Deliveries” list.
An idea about
how to implement a Purchase Order system in this blog would be helpful:
http://ethan-deng.blogspot.jp/2013/03/purchase-order-management-system.html
Best regards,
Patrick
Patrick Liang
TechNet Community Support

How to create purchase order using VA01 for BAPI?

how to create purchase order using VA01 for BAPI?

Hi Arun,
Please check this link
Example Program for BAPI_PO_CREATE1
Re: BAPI_PO_CREATE1
Questions in BAPI_PO_CREATE1
Problem with BAPI_PO_CREATE1
*& Report BAPI_PO_CREATE *
REPORT bapi_po_create.
Input File Declaration
TYPES: BEGIN OF ty_input_file,
column1 TYPE char50,
column2 TYPE char50,
column3 TYPE char50,
column4 TYPE char50,
column5 TYPE char50,
column6 TYPE char50,
column7 TYPE char50,
column8 TYPE char50,
column9 TYPE char50,
column10 TYPE char50,
column11 TYPE char50,
column12 TYPE char50,
column13 TYPE char50,
column14 TYPE char50,
column15 TYPE char50,
column16 TYPE char50,
column17 TYPE char50,
column18 TYPE char50,
END OF ty_input_file.
DATA: i_input_file TYPE STANDARD TABLE OF ty_input_file,
wa_input_file TYPE ty_input_file.
CONSTANTS: c_path TYPE char20 VALUE 'C:\',
c_mask TYPE char9 VALUE ',.,..',
c_mode TYPE char1 VALUE 'O',
c_filetype TYPE char10 VALUE 'ASC',
c_x TYPE char01 VALUE 'X'.
PARAMETERS : p_fname LIKE rlgrap-filename.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_fname.
Browse Presentation Server
PERFORM f4_presentation_file.
START-OF-SELECTION..
Read presentation server file
PERFORM f1003_upload_file.
IF NOT i_input_file[] IS INITIAL.
PERFORM split_data.
ENDIF.
*& Form f4_presentation_file
*& F4 Help for presentation server
FORM f4_presentation_file .
CALL FUNCTION 'WS_FILENAME_GET'
EXPORTING
def_path = c_path
mask = c_mask
mode = c_mode
title = text-001
IMPORTING
filename = p_fname
EXCEPTIONS
inv_winsys = 1
no_batch = 2
selection_cancel = 3
selection_error = 4
OTHERS = 5.
IF sy-subrc 0.
MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.
ENDFORM. " f4_presentation_file
*& Form f1003_upload_file
*& Upload File
FORM f1003_upload_file .
DATA: lcl_filename TYPE string.
lcl_filename = p_fname.
CALL FUNCTION 'GUI_UPLOAD'
EXPORTING
filename = lcl_filename
filetype = c_filetype
has_field_separator = c_x
TABLES
data_tab = i_input_file
EXCEPTIONS
file_open_error = 1
file_read_error = 2
no_batch = 3
gui_refuse_filetransfer = 4
invalid_type = 5
no_authority = 6
unknown_error = 7
bad_data_format = 8
header_not_allowed = 9
separator_not_allowed = 10
header_too_long = 11
unknown_dp_error = 12
access_denied = 13
dp_out_of_memory = 14
disk_full = 15
dp_timeout = 16
OTHERS = 17.
IF sy-subrc 0.
MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
EXIT.
ENDIF.
ENDFORM. " f1003_upload_file
*& Form split_data
Collect data for creating Purchase Order
FORM split_data .
DATA: i_poitem TYPE STANDARD TABLE OF bapimepoitem,
i_poitemx TYPE STANDARD TABLE OF bapimepoitemx,
i_poitem_sch TYPE STANDARD TABLE OF bapimeposchedule,
i_poitem_schx TYPE STANDARD TABLE OF bapimeposchedulx,
i_acct_*** TYPE STANDARD TABLE OF bapimepoaccount,
i_acct_assx TYPE STANDARD TABLE OF bapimepoaccountx,
i_services TYPE STANDARD TABLE OF bapiesllc ,
i_srvacc TYPE STANDARD TABLE OF bapiesklc,
i_return TYPE STANDARD TABLE OF bapiret2,
wa_header TYPE bapimepoheader,
wa_headerx TYPE bapimepoheaderx,
wa_poitem TYPE bapimepoitem,
wa_poitemx TYPE bapimepoitemx,
wa_poitem_sch TYPE bapimeposchedule,
wa_poitem_schx TYPE bapimeposchedulx,
wa_acct_*** TYPE bapimepoaccount,
wa_acct_assx TYPE bapimepoaccountx,
wa_services TYPE bapiesllc,
wa_srvacc TYPE bapiesklc,
wa_return TYPE bapiret2,
ws_po TYPE bapimepoheader-po_number.
break gbpra8.
wa_services-pckg_no = 10.
wa_services-line_no = 1.
wa_services-outl_no = '0'.
wa_services-outl_ind = c_x.
wa_services-subpckg_no = 20.
APPEND wa_services TO i_services.
wa_srvacc-pckg_no = 10.
wa_srvacc-line_no = 1.
wa_srvacc-serno_line = 01.
wa_srvacc-serial_no = 01.
wa_srvacc-percentage = 100.
APPEND wa_srvacc TO i_srvacc.
LOOP AT i_input_file INTO wa_input_file.
IF wa_input_file-column2 EQ 'HD'.
wa_header-doc_type = wa_input_file-column3.
wa_header-creat_date = sy-datum.
wa_header-created_by = sy-uname.
wa_header-vendor = wa_input_file-column4.
PERFORM conversion_output USING wa_header-vendor
CHANGING wa_header-vendor.
wa_header-comp_code = 'DE03'.
wa_header-purch_org = 'DE03'.
wa_header-pur_group = 'DE1'.
wa_header-vper_start = wa_input_file-column9.
wa_header-vper_end = wa_input_file-column10.
wa_headerx-comp_code = c_x.
wa_headerx-doc_type = c_x.
wa_headerx-creat_date = c_x.
wa_headerx-created_by = c_x.
wa_headerx-vendor = c_x.
wa_headerx-purch_org = c_x.
wa_headerx-pur_group = c_x.
wa_headerx-vper_start = c_x.
wa_headerx-vper_end = c_x.
ENDIF.
IF wa_input_file-column2 EQ 'IT'.
wa_poitem-po_item = wa_input_file-column3.
wa_poitem-short_text = wa_input_file-column6.
wa_poitem-plant = wa_input_file-column8.
wa_poitem-quantity = '1'.
wa_poitem-tax_code = 'V0'.
wa_poitem-item_cat = 'D'.
wa_poitem-acctasscat = 'K'.
wa_poitem-matl_group = wa_input_file-column7.
wa_poitem-pckg_no = '10'.
APPEND wa_poitem TO i_poitem .
wa_poitemx-po_item = wa_input_file-column3.
wa_poitemx-po_itemx = c_x.
wa_poitemx-short_text = c_x.
wa_poitemx-plant = c_x.
wa_poitemx-quantity = c_x.
wa_poitemx-tax_code = c_x.
wa_poitemx-item_cat = c_x.
wa_poitemx-acctasscat = c_x.
wa_poitemx-matl_group = c_x.
wa_poitemx-pckg_no = c_x.
APPEND wa_poitemx TO i_poitemx.
wa_poitem_sch-po_item = wa_input_file-column3.
wa_poitem_sch-delivery_date = sy-datum.
APPEND wa_poitem_sch TO i_poitem_sch.
wa_poitem_schx-po_item = wa_input_file-column3.
wa_poitem_schx-po_itemx = c_x.
wa_poitem_schx-delivery_date = c_x.
APPEND wa_poitem_schx TO i_poitem_schx.
wa_acct_***-po_item = 10.
wa_acct_***-serial_no = 01.
wa_acct_***-gl_account = '0006360100'.
wa_acct_***-co_area = '1000'.
wa_acct_***-costcenter = 'KC010000'.
APPEND wa_acct_*** TO i_acct_***.
wa_acct_***-po_item = 10.
wa_acct_***-serial_no = 02.
wa_acct_***-gl_account = '0006360100'.
wa_acct_***-co_area = '1000'.
wa_acct_***-costcenter = 'KC010000'.
APPEND wa_acct_*** TO i_acct_***.
wa_acct_assx-po_item = 10.
wa_acct_assx-serial_no = 01.
wa_acct_assx-po_itemx = c_x.
wa_acct_assx-serial_nox = c_x.
wa_acct_assx-gl_account = c_x.
wa_acct_assx-co_area = c_x.
wa_acct_assx-costcenter = c_x.
APPEND wa_acct_assx TO i_acct_assx.
wa_acct_assx-po_item = 10.
wa_acct_assx-serial_no = 02.
wa_acct_assx-po_itemx = c_x.
wa_acct_assx-serial_nox = c_x.
wa_acct_assx-gl_account = c_x.
wa_acct_assx-co_area = c_x.
wa_acct_assx-costcenter = c_x.
APPEND wa_acct_assx TO i_acct_assx.
wa_services-pckg_no = 20.
wa_services-line_no = 2.
wa_services-service = wa_input_file-column9.
wa_services-quantity = '100'.
wa_services-gr_price = '100'.
wa_services-userf1_txt = wa_input_file-column13.
APPEND wa_services TO i_services.
wa_srvacc-pckg_no = 20.
wa_srvacc-line_no = 1.
wa_srvacc-serno_line = 02.
wa_srvacc-serial_no = 02.
wa_srvacc-percentage = 100.
APPEND wa_srvacc TO i_srvacc.
ENDIF.
ENDLOOP.
CALL FUNCTION 'BAPI_PO_CREATE1'
EXPORTING
poheader = wa_header
poheaderx = wa_headerx
POADDRVENDOR =
TESTRUN =
MEMORY_UNCOMPLETE =
MEMORY_COMPLETE =
POEXPIMPHEADER =
POEXPIMPHEADERX =
VERSIONS =
NO_MESSAGING =
NO_MESSAGE_REQ =
NO_AUTHORITY =
NO_PRICE_FROM_PO =
IMPORTING
exppurchaseorder = ws_po
EXPHEADER =
EXPPOEXPIMPHEADER =
TABLES
return = i_return
poitem = i_poitem
poitemx = i_poitemx
POADDRDELIVERY =
poschedule = i_poitem_sch
poschedulex = i_poitem_schx
poaccount = i_acct_***
POACCOUNTPROFITSEGMENT =
poaccountx = i_acct_assx
POCONDHEADER =
POCONDHEADERX =
POCOND =
POCONDX =
POLIMITS =
POCONTRACTLIMITS =
poservices = i_services
posrvaccessvalues = i_srvacc
POSERVICESTEXT =
EXTENSIONIN =
EXTENSIONOUT =
POEXPIMPITEM =
POEXPIMPITEMX =
POTEXTHEADER =
POTEXTITEM =
ALLVERSIONS =
POPARTNER =
break gbpra8.
LOOP AT i_return INTO wa_return.
ENDLOOP.
ENDFORM. " split_data
*& Form conversion_output
Conversion exit input
FORM conversion_output USING p_ip
CHANGING p_op.
CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
EXPORTING
input = p_ip
IMPORTING
output = p_op.
ENDFORM. " conversion_output
Best regards,
raam

SRM SUS..can supplier create purchase orders

Hi,
In SRM SUS ( Supplier self service)
1) Is it possible that Supplier/Vendors can able to create purchase orders himself
2) Can Supplier/vendors able to access cataloges
3)Can supplier create confirmation himself for both goods , as i knows it is possible for service confimations
Thx
Jai

Hi Jairaj,
In SRM SUS ( Supplier self service)
1) Is it possible that Supplier/Vendors can able to create purchase orders himself
No. The Vendors change can accept or reject PO Lines and change the price.
They can create POR.
2) Can Supplier/vendors able to access cataloges
No.
3)Can supplier create confirmation himself for both goods , as i knows it is possible for service confimations
The vendors can create Service entry sheet in SRM 7.0.
The vendors can create ASN for materials.
Regards,
Pavan

Order cannot be placed using "Create sales order" fiori app

We have setup "create sales order" fiori app and tried to place a order. We encountered with the error saying "In the context of Data Services an unknown internal server error occured" whilst clicking "Checkout" button.
We looked up Error log and found the detailed error "Invalid format (return table): Row Number 1, Property Name 'SalesOrderSimulation', Property Value". Full error log xml is as follows,
<?xml version="1.0" ?>
- <ERROR_CONTEXT>
<ERROR_INFO>Invalid format (return table): Row Number 1, Property Name 'SalesOrderSimulation', Property Value ''</ERROR_INFO>
- <ERROR_RESOLUTION>
<SAP_NOTE>See SAP Note 1797736 for error analysis</SAP_NOTE>
<LINK_TO_SAP_NOTE>https://service.sap.com/sap/support/notes/1797736</LINK_TO_SAP_NOTE>
</ERROR_RESOLUTION>
<_-IWCOR_-CX_DS_INTERNAL_ERROR />
- <_-IWCOR_-CX_DS_EP_ENTITY_ERROR>
<INDEX>1</INDEX>
<PROPERTY>SalesOrderSimulation</PROPERTY>
</_-IWCOR_-CX_DS_EP_ENTITY_ERROR>
- <_-IWCOR_-CX_DS_EP_PROPERTY_ERROR>
<PROPERTY>SalesOrderSimulation</PROPERTY>
<VALUE />
<TYPE>\TYPE=STRING</TYPE>
<OFFSET>0</OFFSET>
</_-IWCOR_-CX_DS_EP_PROPERTY_ERROR>
- <CX_PARAMETER_INVALID_TYPE>
<TYPE>\TYPE=STRING</TYPE>
</CX_PARAMETER_INVALID_TYPE>
- <SERVICE_INFO>
<NAMESPACE>/SAP/</NAMESPACE>
<SERVICE_NAME>***Hide_due_to_secure_log_level***</SERVICE_NAME>
<VERSION>0001</VERSION>
<SYSTEM_ALIAS>LOCAL</SYSTEM_ALIAS>
<DESTINATION>NONE</DESTINATION>
</SERVICE_INFO>
- <SYSTEM_INFO>
<REQUEST_URI>/sap/opu/odata/sap/***Hide_due_to_secure_log_level***</REQUEST_URI>
<REMOTE_ADDRESS>xxx.xx.x.xx</REMOTE_ADDRESS>
<APPLICATION_SERVER>eccdev_ECD_10</APPLICATION_SERVER>
<HUB_VERSION_INFO>System ECD/200, NW Release 7.40, SAP_GWFND SP10, Internal GWFND Version 011</HUB_VERSION_INFO>
</SYSTEM_INFO>
</ERROR_CONTEXT>
Please look at the screenshot for more details on request.
Do you have any idea how to fix this bug or do we have a mistake in our configuration?
Thanks for any hints.

Have you been able to solve this issue without resorting to a core mod described by Gopichand above? In our system the notes referenced by Masa in another post are not applicable because of the SP-level of the components involved. We've got:
SAP_GWFND
740
0010
SAP Gateway Foundation 7.40
SAP_UI
740
0011
User Interface Technology 7.40
SRA017
600
0006
Create Purchase Order OData Integration
UIEAAP01
100
0005
UI for ERP Central Applications
UIX01CA1
100
0004
UI for Cross-Applications
UIX01EAP
100
0005
UI for ERP Central Applications
Based on the fact that the error seems to be caused by the mismatching types of the SalesOrderSimulation property, the component at fault is SRA017 or possibly the GWFND component itself. In another system we're on SRA017 SP5 and SAP_GWFND SP9 and the app works without an issue. Since both those SP's are 1 level lower, it further confirms that it must be SRA017 SP6 or SAP_GWFND SP10 that cause the issue.
I have not been able to find any recent OSS notes that would address the issue and will be opening an OSS incident for it. If you happen to already have a solution, then please let me know. If not, I'll provide an update once I've heard from OSS folks.
Lukasz

Returns item from purchase order in SRM

Hi,
Is it possible to return item from a purchase order in SRM?
meaning : to return goods to an external vendor.
in ECC i know its possible. but i want to know if its possible in SRM.
if yes, how?
(i dont want to return by confirmation)
we are using SRM550.
regards,
vered
Edited by: Vered Madar on Aug 2, 2010 1:28 PM

Hi,
In SRM POs, GR based invoice indicator for Goods item is ticked based on the Vendor Master. If the vendor master has the tick, then PO will have the tick for GR based invoice. However for a service PO/limit PO, GR based invoice comes as default in PO and cannot be undone.
Regards,
Sanjeev

Update was terminated while creating purchase order from ME21N

Hi Experts,
We are getting this dump when try to create purchase order from ME21N;
Our system ECC 6.0 and IS-AFS (Apparel & Footwear Solution) V600 component has installed,
How can we prevent this error,
Regards
Here is the dump and sm21 log,
Runtime Errors         LOAD_PROGRAM_NOT_FOUND
Exception              CX_SY_PROGRAM_NOT_FOUND
Date and Time          10.10.2008 10:22:03
Short text
     Program "RMCMS431 " not found.
What happened?
     There are several possibilities:
     Error in the ABAP Application Program
     The current ABAP program "SAPLMCS4" had to be terminated because it has
     come across a statement that unfortunately cannot be executed.
     or
     Error in the SAP kernel.
     The current ABAP "SAPLMCS4" program had to be terminated because the
     ABAP processor detected an internal system error.
What can you do?
     Note down which actions and inputs caused the error.
     To process the problem further, contact you SAP system
     administrator.
    Using Transaction ST22 for ABAP Dump Analysis, you can look
    at and manage termination messages, and you can also
    keep them for a long time.
Error analysis
    An exception occurred that is explained in detail below.
    The exception, which is assigned to class 'CX_SY_PROGRAM_NOT_FOUND', was not
     caught in
    procedure "TMC2F_FROUT_CALL" "(FORM)", nor was it propagated by a RAISING
     clause.
    Since the caller of the procedure could not have anticipated that the
    exception would occur, the current program is terminated.
    The reason for the exception is:
    On account of a branch in the program
    (CALL FUNCTION/DIALOG, external PERFORM, SUBMIT)
    or a transaction call, another ABAP/4 program
    is to be loaded, namely "RMCMS431 ".
    However, program "RMCMS431 " does not exist in the library.
    Possible reasons:
    a) Wrong program name specified in an external PERFORM or
       SUBMIT or, when defining a new transaction, a new
       dialog module or a new function module.
    b) Transport error
How to correct the error
    Check the last transports to the R/3 System.
    Are changes currently being made to the program "SAPLMCS4"?
    Has the correct program been entered in table TSTC for Transaction "ME21N "?
    If the error occures in a non-modified SAP program, you may be able to
    find an interim solution in an SAP Note.
    If you have access to SAP Notes, carry out a search with the following
    keywords:
    "LOAD_PROGRAM_NOT_FOUND" "CX_SY_PROGRAM_NOT_FOUND"
    "SAPLMCS4" or "LMCS4F10"
    "TMC2F_FROUT_CALL"
    If you cannot solve the problem yourself and want to send an error
    notification to SAP, include the following information:
    1. The description of the current problem (short dump)
       To save the description, choose "System->List->Save->Local File
    (Unconverted)".
    2. Corresponding system log
       Display the system log by calling transaction SM21.
       Restrict the time interval to 10 minutes before and five minutes
    after the short dump. Then choose "System->List->Save->Local File
    (Unconverted)".
    3. If the problem occurs in a problem of your own or a modified SAP
    program: The source code of the program
       In the editor, choose "Utilities->More
    Utilities->Upload/Download->Download".
    4. Details about the conditions under which the error occurred or which
    actions and input led to the error.
    The exception must either be prevented, caught within proedure
    "TMC2F_FROUT_CALL" "(FORM)", or its possible occurrence must be declared in the
    RAISING clause of the procedure.
    To prevent the exception, note the following:
sm21 log ;
Transaction Canceled 00 671 ( LOAD_PROGRAM_NOT_FOUND 20081010102203saptest_TET_00 EYUCE 100
Update terminated
> Update key: F39796DD5421F1509233001E0BD601E0
> Update module: MCE_STATISTICS_UPD_V2
Run-time error "LOAD_PROGRAM_NOT_FOUND" occurred

Please follow the oss note 800335
V2 Update terminations in Purchasing transactions after upgrading or installing AFS 5.0 release.
Other terms
AFS, LIS, MIGO, ME22N, OLI3, S433, S431
Reason and Prerequisites
AFS Purchasing infostructure S431 is no longer used. S433 is the valid infostructure for the release AFS 5.0.
Solution
Please do the following.
For customers upgrading to AFS 5.0 only:
> Rebuild Infostructure S433.
- Goto transaction: OLI3 (Statistical Set up of Infostructures)
- Info structure to be compile: S433
- Specify the 'Name of run'.
- Execute.
> Please also follow the instructions given below.
For both Upgrade and Non-upgrade Customers:
> Create the report 'ZDELS431'.
- Transaction: SE38
- Give Program name as ZDELS431.
- Create (F5).
- Title : 'Program to delete S431'.
- Type : 1 (Executable Program).
- Status: T (Test Program).
> Copy the program text from the note and paste in the program.
> Save and activate the program.
> Execute the report for all clients in Update mode.
(Two check-boxes will appear: P_ALL_CL, P_UPDATE.
   Please check both of them).
This report will delete all the references to infostructure S431.

Procure-to-Pay Scenario. Create Purchase Order

Hello Experts: I have a question regarding the Procure-to-Pay scenario and the Create PO functionality.
we are in SRM 7.0, Classic Scenario and we try to implement the Procure-to-Pay functionality as it is described in OSS note 1263876 "SAP SRM: Configuration of Procure-to-Pay Scenario".
Our idea is to transfer Purchase Requisitions from ECC6 to SRM using the CPPR application. But we will also take advantage of the integration with MM provided with this scenario.
If you are familiar with this, you will already know that, using the harmonized role for operational purchaser (ERP/SRM) an end user can create Purchase Orders in the backend. Our question is related to this functionality.
Using this role, the buyer can select Purchasing Documents under the detailed navigation area and, from there, he will have access to create Shopping carts, Purchase requisitions, Purchase Orders and Purchase order responses.
If we select Create Purchase Order, the application "Purchase Order: New" gets opened. Here we have to select the system where we want to create the new PO: either SRM or ECC6. Our first question is: As we are running a Classic scenario, why are we asked to select between SRM and ECC6?. It should be only ECC6, shouldn't be?
In any case, the SRM systems gets selected by default when we open "Purchase Order: New" appl. and bellow this field, you can see the PO types customized in SRM. If we change the system to ECC6 we see the following: "Number of purchase order types: 0" . So, no PO types are available. this is the second question: why do we have 0 PO types to be created when we select the ECC6 system? is there a missing customizing where we have to define which document types are vaialable to create POs in ECC6 from SRM Portal?.
To summarize: only ECC6 should be proposed as system to create POs (as we are running a Classic Scenario) and there should be ECC6 PO types available to create such POs in the ECC6.
Can you please tell us what is still missing in our configuration? Any help will be more than welcome
Many thanks in advance for your valuable help
Best regards
Valentí

The purpose of MRP run is to make sure that you always have enough stock.
An order to cost center will not increase stock.
Means: MRP is not able to create requisitions for cost center consumption. If you change a requisition created by MRP to be ordered to a cost center, then the next MRP run will create a new requisition to stock.

Archive Purchase Order on SRM

Hi experts,
I'm working on the SRM archive process. I'm in extended classic scenario so my purchase order is created on SRM and duplicated on ECC. I only want to archive purchase order on SRM and not on ECC.
When the user is looking for the purchase order on ECC how does he know that the order is archived on SRM ?
Thank you for your help.
Regards,
Mikaël.

Hi Peter,
Thank you for your answer.
I will used a cutomer field on the ECC purchase order and create a specific program to update this customer field from SRM data and tables ZARIX...
Thanks,
Mikaël.

Error creating Purchase Order

Hi Gurus,
I've this issue. I'm using SRM 5.0.
I've configured a product category mentioning it needs to go to sourcing only when the vendor is not mentioned. Otherwise it should bypass sourcing and after the last approval the PO has to be created in backend automatically. We are using Classic Scenario. Now i've this issue. When I create a shopping cart without vendor it goes to sourcing cockpit and from there when I fill the vendor information and create purchase order, purchase order gets created in backend. BUT when I provide vendor information in the shopping cart and Order it after all approvals, it doesn't create PO in backend. Instead I see an error in the error logs of Shopping cart mentioning.
<b>"Shopping cart 0040000365: Error creating the follow-on document"
</b>
I see this under <b> Application Monitors > Shopping cart > Local Errors </b>
Could someone please help me if there knows the solution for this or any note available for this.
Regards,
Sam K

Hi Sam,
Check your settings for when Sourcing is carried out. I assume you have setting in
place always external procurement for every product category in place, why every
SC goes to sourcing cockpit. Adjust that setting. You need to work with product
categories to seperate things out or implement BADI for sorting out to individual
needs. In parallel check the settings for the doc type, number range and the follow
on doc to be created from SC.
Cheers,
Claudia

Extended Classic : Unable to create purchase order

Hi All,
We are using SRM5.0 system, i did required configuration for extended classic. I defined number ranges for local and backend purchase orders. But after creating SC, system is unable to create purchase order. Shopping cart is not ended up in error. In BBP_PD, I found that number generated for purchase order is always 1.
Please advise.
Regards,
Raj

are the RFC connections between SRM system and R/3 systems working? please check this.
transaction --> SM59 --> is used for maintaining RFC destination.

Cannot use create purchase order in SRM 7.01

Similar Messages

Maybe you are looking for