BAPI - SD_SALESDOCUMENT_CREATE Condtion Subroutine Dump

[VenkatRamesh_V]

Dear Experts,

I am creating sale order via bapi SD_SALESDOCUMENT_CREATE

While passing Pricing condition's to bapi, Dump raised

'PERFORM_PARAMETER_MISSING' While checking in abap editor,

perform xkomv_lesen_direkt(sapmj3as)
using fkonvkom-kposn
fkonvkom-kschl
fkonvkom-j_3aetenr
1
changing sy-subrc.

"Program name MJ3ASF6A

FORM XKOMV_LESEN_DIREKT USING US_POSNR LIKE KOMV-KPOSN
US_KSCHL LIKE KOMV-KSCHL
US_ETENR LIKE KOMV-J_3AETENR "AFS
US_TABIX LIKE J_3ACOND-IX_XKOMV "AFS
US_ZAEHK LIKE KOMV-ZAEHK "Missing
CHANGING VALUE(CH_SUBRC) LIKE SY-SUBRC.

Kindly suggest me to solve.

Regards,

Ramesh

[Jelena]

There is a missing parameter when calling the routine. The error seems rather self-explanatory though.

SD_SALES_CONDITION_MAINTAIN is not a BAPI. It's an unreleased function module (i.e. the customers should not really be using it).

Also it does not create sales orders. Very much confused by this question...

[VenkatRamesh_V]

I am passing to SD_SALES_CONDITION_MAINTAIN Dump Raised. In St22 Transaction code by clicking the abap editor it gone to the FM module SD_SALES_CONDITION_MAINTAIN.

In standard perform 4 input passed. but in form 5 inputs where declared. Suggest me notes to correct the error.

perform xkomv_lesen_direkt(sapmj3as)
using fkonvkom-kposn "1
fkonvkom-kschl "2
fkonvkom-j_3aetenr "3
1 "4
changing sy-subrc.

FORM XKOMV_LESEN_DIREKT USING US_POSNR LIKE KOMV-KPOSN "1
US_KSCHL LIKE KOMV-KSCHL "2
US_ETENR LIKE KOMV-J_3AETENR "AFS "3
US_TABIX LIKE J_3ACOND-IX_XKOMV "AFS "4
US_ZAEHK LIKE KOMV-ZAEHK "Missing "5 Missing.
CHANGING VALUE(CH_SUBRC) LIKE SY-SUBRC.

Hope you understand.

Regards,

Ramesh

[VenkatRamesh_V]

Dear Experts,

I tried all Bapi's.

/AFS/BAPI_SALESORD_CREATEFDATA,

BAPI_SALESORDER_CREATEFROMDAT2,

SD_SALESDOCUMENT_CREATE -Same error PERFORM_PARAMETER_MISSING Dump Raised While passing pricing condtions.

Version -EHP7 AFS

Kindly suggest me how to solve.

Regards,

Ramesh

[raymond_giuseppi]

Did you check thru version management of include MJ3ASF6A and caller program or directly in SNOTE filtering on component IS-AFS-SD for partially/recently implemented OSS notes on your system?

[VenkatRamesh_V]

Sir,

I Already checked program, no version no generated. Basis consultant left job. not able to find which note.

[kiran_k8]

A Developer will be searching for a relevant note in SAP Service Market Place and Basis Consultant will help in confirming the System data like Component Version/Installation Number/Support package details etc.

If you don't find any note relevant atleast from the Functionality and Code point of view, you can raise an OSS message,if you are authorised to.

K.Kiran.

[VenkatRamesh_V]

While creating Sale order in VA01 no Dump raised. but passing the data to BAPI Dump Raised. Project Manager instructed to change the BAPI. Tried All BAPI'S, Searched with the error message in Google not able to find the Notes related information.

[Jelena]

Well, maybe the problem then is with the way how you are calling BAPI? But you haven't shared your code.

If you believe there is an error in standard then open an incident with SAP Support.

[VenkatRamesh_V]

My Code.

CLEAR vbak.
SELECT SINGLE * FROM vbak INTO vbak WHERE vbeln = p_wa_pack_det-sorder.

header-doc_type = 'ZPO'.
headerx-doc_type = 'ZPO'.
header-sales_org = vbak-vkorg.
headerx-sales_org = 'X'.
header-distr_chan = vbak-VTWEG. "Added on 15/6/2016
headerx-distr_chan = 'X'.
header-division = vbak-spart.
header-req_date_h = sy-datum.
header-purch_date = sy-datum.
headerx-division = 'X'.
headerx-updateflag = 'I'.

header-COMP_CDE_B = vbak-BUKRS_vf.
headerX-COMP_CDE_B = 'X'.

MOVE-CORRESPONDING header TO header_afs. "AFS
MOVE-CORRESPONDING headerX TO headerx_afs."AFS
APPEND header.
APPEND headerx.

partner-partn_role = 'AG'. "<-- SOLD TO PARTY
partner-partn_numb = vbak-kunnr.
MOVE-CORRESPONDING partner TO wa_partner_afs.
APPEND partner.
APPEND wa_partner_afs TO partner_afs. "A 16/10/2017

partner-partn_role = 'WE'. "<-- SHIP TO PARTY
partner-partn_numb = vbak-kunnr.
MOVE-CORRESPONDING partner TO wa_partner_afs.
APPEND partner.
APPEND wa_partner_afs TO partner_afs. "A 16/10/2017

item-itm_number = p_item.
item-material = p_packing-style.
item-target_qty = P_INVOICEQTY.
item-SHORT_TEXT = P_INVE-arktx.
item-REF_DOC = p_packing-sorder.
*item-plant =
MOVE-CORRESPONDING item TO wa_item_afs. "A 16/10/2017
APPEND item.
APPEND wa_item_afs TO item_afs. "A 16/10/2017
itemx-itm_number = p_item.
itemx-updateflag = 'I'.
itemx-material = 'X'.
itemx-plant = 'X'.
itemx-store_loc = 'X'.
itemx-target_qty = 'X'.
itemx-REF_DOC = 'X'.
itemx-SHORT_TEXT = 'X'.
APPEND itemx.
MOVE-CORRESPONDING itemx TO wa_itemx_afs. "A 16/10/2017
APPEND wa_itemx_afs TO itemx_afs. "A 16/10/2017

CLEAR lt_schedules_in.
lt_schedules_in-itm_number = p_item.
lt_schedules_in-SCHED_LINE = p_item.
lt_schedules_in-req_qty = P_INVOICEQTY.
MOVE-CORRESPONDING lt_schedules_in TO wa_sch_afs.
APPEND lt_schedules_in.
APPEND wa_sch_afs TO it_sch_afs.

CLEAR lt_schedules_inx.
lt_schedules_inx-itm_number = p_item.
lt_schedules_inx-SCHED_LINE = p_item.
lt_schedules_inx-updateflag = 'X'.
lt_schedules_inx-req_qty = 'X'.
MOVE-CORRESPONDING lt_schedules_inx TO wa_schx_afs.
APPEND lt_schedules_inx.
APPEND wa_schx_afs TO it_schx_afs.

*sales_conditions_in-cond_updat = 'X'.
lt_sales_conditions_in-COND_TYPE = 'PR00'.
*lt_sales_conditions_in-COND_ST_NO = '100'.
*lt_sales_conditions_in-COND_COUNT = '1'.
lt_sales_conditions_in-ITM_NUMBER = p_item.
lt_sales_conditions_in-cond_value = P_INVOICEPRICE.
*lt_sales_conditions_in-CONBASEVAL = P_INVOICEPRICE.
lt_sales_conditions_in-CURRENCY = vbak-waerk.

lt_sales_conditions_inx-updateflag = 'I'.
lt_sales_conditions_inx-cond_value = 'X'.
lt_sales_conditions_inx-ITM_NUMBER = p_item.
lt_sales_conditions_inx-CURRENCY = 'X'.
lt_sales_conditions_inx-COND_TYPE = 'PR00'.
lt_sales_conditions_inx-COND_VALUE = 'X'.
*lt_sales_conditions_inx-COND_ST_NO = '100'.
*lt_sales_conditions_inx-COND_COUNT = '1'.
APPEND lt_sales_conditions_inx.
APPEND lt_sales_conditions_in.
MOVE-CORRESPONDING lt_sales_conditions_in TO wa_cond_afs.
wa_cond_afs-SCHED_LINE = '1'.
APPEND wa_cond_afs TO it_cond_afs.

SPAN { font-family: "Courier New"; font-size: 10pt; color: #000000; background: #FFFFFF; } .L0S31 { font-style: italic; color: #808080; }

*CALL FUNCTION 'SD_SALESDOCUMENT_CREATE'
* EXPORTING
** SALESDOCUMENT =
* sales_header_in = header
* sales_header_inx = headerx
* TESTRUN = 'X'
* IMPORTING
* salesdocument_ex = lv_order
* TABLES
* return = return
* sales_items_in = item
* sales_items_inx = itemx
* sales_partners = partner
* sales_schedules_in = lt_schedules_in
* sales_schedules_inx = lt_schedules_inx
* SALES_CONDITIONS_IN = lt_SALES_CONDITIONS_IN
* SALES_CONDITIONS_INX = lt_SALES_CONDITIONS_INX.

Regards,

Ramesh

[Jelena]

Please use "comment on this answer" when responding to an existing answer. If you post a new answer then no one gets notified about it. Also if it's not actually an answer it's confusing to the readers.

Thank you.

[Jelena]

When calling BAPI, we only need to include the manual pricing conditions. If pricing can be determined based on the condition records then we don't need to send any pricing information. Not sure how PR00 is configured in your system.

Other that that, based on the fact that one standard routine calls another standard routine incorrectly I'd go ahead and contact SAP Support. We don't have this program in our system, so I can't tell what else is in it and what is it's purpose.

[VenkatRamesh_V]

Thank you for replying.

Kindly see the attachment.

Regards,

Ramesh