Unable to create sales transaction in POSDM though BAPI

Hi
ICurrently I am trying to create sales transaction in POSDM which is coming from POS thru XI to POSDM. But the BAPI /POSDW/CREATE_TRANSACTIONS_EXT is throwing an error
" Error determining sales item category for code 2001"
It was working perfectly fine in development. I have imported all transports from development to quality sytem. we also have BI plant and article data in our system. But not sure if anything other than this needs to be done.
Thanks
Naina

Hi Amit,
I would recommend you to raise the same query in the forumSAP CRM: Mobile Applications which is dedicated to queries related to mobile application and where you have more chances of getting the answer.
<b>Reward points if my post helps!!</b>
Best regards,
Vikash

Similar Messages

Error message while creating Sales transaction

Hi Gurus
While creating a sales transaction in Mobile Sales I am getting the following error message.
No Valid sales channel exists for this business partner enters a sales channel in the business partner sales area data.
I have checked in table SMO_KNVV, there is an entry for this business partner. What can be the possible reason? Please help.
Regards
Javed

Hi Javed,
Your logged employee should also have some sales area assigned to him/her.
This can be done by assigning you employee to sales position under sales area in CRM Org Management (PPOMA_CRM).
Once this is done and org. data is replicated to Mobile. you can very much create the transactions without error.
Best Regards,
Pratik Patel
<b>Reward with Points!</b>

Unable to create a transacted JMS Session

          We have some code that worked perfectly under wls7.0 and earlier, but refuses to
          work under wls8.1. In our situation, we are unable to create a JMS Session with
          internal transactions.
          The result of the following code
          System.out.println("transacted_=" + transacted_);
          tsession=tcon.createTopicSession(transacted_, Session.AUTO_ACKNOWLEDGE);
          System.out.println("session.getTransacted()=" + tsession.getTransacted());
          is the following
          transacted_=true
          session.getTransacted()=false
          We have tried using xa true and false; but commonly use false.
          //from config.xml
          <JMSConnectionFactory JNDIName="corej2ee.jms.JMSConnectionFactory"
          Name="CoreJMSConnectionFactory" Targets="myserver"/>
          thanks,
          jim


An alternative is to modify the servlet code to use global (user)
          transactions instead of local (transacted session)
          transactions - the performance will likely be the same in your case -
          or may actually improve due to the activation of the pooling code.
          jim stafford wrote:
          > You were correct about us using the resource-ref. The documentation seemed to indicate
          > that our servlet code should have worked as initially developed, however the new
          > changes work
          >
          > //replace resource-ref lookup with env-entry to allow transacted JMS
          > //sessions. This is new with wls8.1
          > //tconFactory = (TopicConnectionFactory)
          > // ctx.lookup("java:comp/env/jms/topicFactory");
          > String factoryName =
          > (String)ctx.lookup("java:comp/env/jms/myConnectionFactory");
          > System.out.println("using global jndi name:" + factoryName);
          > tconFactory = (TopicConnectionFactory)
          > ctx.lookup(factoryName);
          > tcon = tconFactory.createTopicConnection();
          >
          > System.out.println("transacted_=" + transacted_);
          > tsession=tcon.createTopicSession(transacted_, Session.AUTO_ACKNOWLEDGE);
          > System.out.println("session.getTransacted()=" + tsession.getTransacted());
          >
          > --- output
          > Looking up topic connection factory
          > using global jndi name:corej2ee.jms.JMSConnectionFactory
          > transacted_=true
          > session.getTransacted()=true
          >
          > Tom Barnes <[email protected]> wrote:
          >
          >>Hi Jim,
          >>
          >>My first thought is that the app is running
          >>on the WL server and that the app is using EJB "resource
          >>references" to indirectly access its JMS resources.
          >>Stricter J2EE compliance in 8.1 causes JMS resources
          >>accessed via resource references to ignore the transacted flag.
          >>
          >>See "J2EE Compliance" under:
          >>http://edocs.bea.com/wls/docs81/jms/j2ee_components.html#1033768
          >>
          >>The work-around is to directly specify the JNDI name
          >>of the CF in the app directly instead of looking it up
          >>via a resource reference.
          >>
          >>Please let me know if this helps.
          >>
          >>Tom
          >>
          >>jim stafford wrote:
          >>
          >>
          >>>We have some code that worked perfectly under wls7.0 and earlier, but
          >>
          >>refuses to
          >>
          >>>work under wls8.1. In our situation, we are unable to create a JMS
          >>
          >>Session with
          >>
          >>>internal transactions.
          >>>
          >>>The result of the following code
          >>>
          >>>System.out.println("transacted_=" + transacted_);
          >>>tsession=tcon.createTopicSession(transacted_, Session.AUTO_ACKNOWLEDGE);
          >>>System.out.println("session.getTransacted()=" + tsession.getTransacted());
          >>>
          >>>is the following
          >>>
          >>>transacted_=true
          >>>session.getTransacted()=false
          >>>
          >>>We have tried using xa true and false; but commonly use false.
          >>>
          >>>//from config.xml
          >>><JMSConnectionFactory JNDIName="corej2ee.jms.JMSConnectionFactory"
          >>> Name="CoreJMSConnectionFactory" Targets="myserver"/>
          >>>
          >>>thanks,
          >>>jim
          >>
          >

Unable to create Sales order from "BAPI_SALESORDER_CREATEFROMDAT2" for Free Goods

Hi Experts,
I am facing the issue while creating the Sales order through "BAPI_SALESORDER_CREATEFROMDAT2" , all is going well in normal cases but when I process the contract with FREE GOODS line items for which free goods condition record is maintained it fails to create the Sales order. Is there any special treatment for this Free goods case. Is there any Flag to be passed from BAPI?
Regards,

Hi Paaavan
You can set a break-point include "FV45PFAP_VBAP_BEARBEITEN_VORBE" that is called by both the SAP Standard and BAPI where the data is prepared and checked in the internal table XVBAP. Compare both SAP standard VA01 and your 'Z' program for what may be different in XVBAP.
I think the problem my be with regards to the business_object number that is hardcoded in the standard function module. It has given me issues before and hence I tend to use the function module SD_SALESDOCUMENT_CREATE to create sales documents with.
Regards,
Marius

MOPZ issue :Unable to create new transaction

Hello All,
We have recently installed ECC6 EHP5 ready, and now want to apply the latest patches for it.
when I try to create new transaction from DSWP-->change Management -->Maintenance Optimizer -->Crete new trasaction it is throwing an error .
I have sufficient authorizations from both ends (solmon system and to my s-user)
Solmon roles -->YY(SOLMAN_BASIS_MAINTAIN)
                            YY(SOLMAN_DSWP_ADMIN)
                            YY(SOLMAN_ISSUE_MGMT_MAIN)
                            YY(SOLMAN_LANDSCAPE_MAIN)
S-User Roles --> Maintain System Data Authorizations
System Details:
EHP1 SOLMON 7.0
AIX5.3/ORACLE 10g
Can any one guide me what is the exact problem and how to avoid the same.
ERROR Log from the dump raised
A RAISE statement in the program "CL_SM_DATA_SENDER_RFC=========CP" raised the
exception
condition "NOT_FOUND".
Since the exception was not intercepted by a superior
program, processing was terminated.
Short description of exception condition:
For detailed documentation of the exception condition, use
Transaction SE37 (Function Library). You can take the called
function module from the display of active calls.
url level error log which showed on the browser
Error when processing your request
What has happened?
The URL http://ussappsm00.corpnet2.com:8055/sap/bc/webdynpro/sap/wda_mopz_plan was not called due to an error.
Note
The following error text was processed in the system PSM : Exception condition "NOT_FOUND" raised.
The error occurred on the application server ussappsm00_PSM_55 and in the work process 0 .
The termination type was: RABAX_STATE
The ABAP call stack was:
Method: GET_DESTINATION of program CL_SM_DATA_SENDER_RFC=========CP
Method: GET_ASSIGNED_SUSERS of program CL_MO_SMP_ADAPTER=============CP
Method: LOAD_SHORT_TEXT of program /1BCWDY/LSBW1CHLCWA0SWHM02KO==CP
Method: LOAD_CONTEXT of program /1BCWDY/LSBW1CHLCWA0SWHM02KO==CP
Method: IF_COMPONENTCONTROLLER~LOAD_CONTEXT of program /1BCWDY/LSBW1CHLCWA0SWHM02KO==CP
Method: HANDLEDEFAULT of program /1BCWDY/LSBW1CHLCWA0SWHM02KO==CP
Method: IF_WDR_VIEW_DELEGATE~WD_INVOKE_EVENT_HANDLER of program /1BCWDY/LSBW1CHLCWA0SWHM02KO==CP
Method: INVOKE_EVENTHANDLER of program CL_WDR_DELEGATING_VIEW========CP
Method: NAVIGATE of program CL_WDR_CLIENT_APPLICATION=====CP
Method: DO_NAVIGATION of program CL_WDR_WINDOW_PHASE_MODEL=====CP
What can I do?
If the termination type was RABAX_STATE, then you can find more information on the cause of the termination in the system PSM in transaction ST22.
If the termination type was ABORT_MESSAGE_STATE, then you can find more information on the cause of the termination on the application server ussappsm00_PSM_55 in transaction SM21.
If the termination type was ERROR_MESSAGE_STATE, then you can search for more information in the trace file for the work process 0 in transaction ST11 on the application server ussappsm00_PSM_55 . In some situations, you may also need to analyze the trace files of other work processes.
If you do not yet have a user ID, contact your system administrator.
Error code: ICF-IE-http -c: 800 -u: RRD42469 -l: E -s: PSM -i: ussappsm00_PSM_55 -w: 0 -d: 20110715 -t: 041437 -v: RABAX_STATE -e: RAISE_EXCEPTION
HTTP 500 - Internal Server Error
Your SAP Internet Communication Framework Team
Awaiting your response.
Best Regards
Rakesh

Hi,
You will need the standard SAP Change Management work center role assigned to you. If custom role it should be derived from this role SAP_SMWORK_CHANGE_MAN
Regards,
Srikishan

Create sales order with reference via BAPI

Hi all,
I would like to know if is it possible to create a sales order with reference using BAPI, that is, I want to create an order from a contract, for example, referencing one or more contract itens. If so, what variable or table should I use?
I think that the most suitable function is
'BAPI_SALESORDER_CREATEFROMDAT2' or should I use another to do this?
I am using release SAP ECC 6.0.
Thanks for any help.
Paulo

yes, you are using right BAPI i.e. BAPI_SALESORDER_CREATEFROMDAT2
You will have to provide ORDER_HEADER_IN in that, Others are optional, even then if you have data for them, Provide it for better performance.
For any confusion related to chosing BAPI : You may go to BAPI transaction and find out the correct BAPI according to ur need. for example sales order relatd BAPI's are
BAPI_SALESORDER_CHANGE :Change Sales Order
BAPI_SALESORDER_CREATEFROMDAT2: Create Sales Order
BAPI_SALESDOCU_CREATEWITHDIA: Create Data Container with Dialog
BAPI_SALESORDER_GETLIST:List of all Orders for Customer
and so on.
Reward if helpful..

Problem with BOM Quant while creating Sales order with reference using BAPI

Dear All,
I am facing problem with creating a slaes order with reference to other sales order by using BAPI_SALESORDER_CREATEFROMDAT2 .
Sales order is getting created but
1. It exploding the BOM means the line items which are not there in the reference SO also coming in the new SO ( all BOM items are coming )
2. Schedule line for BOM header item is getting copied to all sub items of BOM.
Can any one help me out to prevent the above deviations in creating Sales order with reference by using BAPI_SALESORDER_CREATEFROMDAT2.
Note: while passing the parameters to BAPI_SALESORDER_CREATEFROMDAT2
all the data related to items is exactly the same as in the original Sales Order.
Thanks in advnace.
Regards,
John

Hi All,
Can any one help me !!!!!!!!!!
please

Unable to create sales Order/Inquiry object using SAP JCo

Hi All,
Pls can you help me.
I am using BAPI_INQUIRY_CREATEFROMDATA2 and BAPI_Trancation_commit to create Inquiry object.From my Client JCo code there is no error.I debugged the BAPI_Trasaction_commit, there is no error, return code is 0. But th system is not creating Inquiry object. When I try the same from SAP GUI client with exactly the same input parameters it works.
Do I need to set any option/value to commit the Inquiry to the SAP database? How to maintain the same session between the different BAPI's. Is there any issue with Session maintainance? I would appreciate if you can provide me any sample SAP JCo code for creating a Sales Order/Inquiry.
Thanks
mars

Can you put the part of your code that fill the ORDER_PARTNERS table, also you could compare your coding with [Sales order creation using BAPI|http://wiki.sdn.sap.com/wiki/display/Snippets/SalesordercreationusingBAPI] in [Community Code Gallery |http://wiki.sdn.sap.com/wiki/display/Snippets/CommunityCodeGallery] (don't forget that there is a conversion exit on the partner role, so use internal codes "AG" and "WE")
Regards,
Raymond

Unable to create unique transaction, please try again later!

What do I do with this message? My paypal works great and im having no problems. But when I try to buy an item from some sites I get this message over and over again. Do I need to edit some of my paypal settings in order to get this away. please help me out. Thanks.

Hi zkessler -- I sent you a private message about your post so we can see what's going on and help you out. Please get back to me when you're able. Thanks!
Karl
Verizon Support
Notice: Content posted by Verizon employees is meant to be informational and does not supersede or change the Verizon Forums User Guidelines or Terms or Service, or your Customer Agreement Terms and Conditions or Plan.

Issue in creating Sales Order in CRM 7.0 IC WEB

Hello Experts,
I am working on CRM7 and ECC 6 integration. I have configured Sales Order ( transaction type ZOR) in CRM. Using GUI the sales order is properly created in CRM and getting replicated to ECC without any issues.
I started configuring IC web UI, systematically followed C04 and C78 and completed all the steps including IC_BT transaction profile customization but inspite of this I am unable to create sales order in IC web.
I am geting error "No transaction type available for creating transactions" and if I go into details of this error it shows a page as follows
Diagnosis
No transaction type is available when creating a transaction. This can be due to the following reasons:
u2022     No transaction type is available according to Customizing
u2022     The user has no authorization for the transaction type
System Response
It is not possible to create the transaction.
Procedure
Make sure that:
u2022     The transaction type is set up in Customizing
u2022     The user has authorization for the transaction type
I have checked everything , nothing seems to be wrong. Can anyone advice how to resolve this issue
Thanks and Regards
Ambar

goto IMG where you defined the ZOR. Select the ZOR and choose Channel on the left, is ICW Interaction Center Webclient a choice? or add it.
We noticed that once any transaction was set to an option, we had to set these for all transactions in the ICWC, ISA, Gui, etc.

Payment Terms in Sales Transaction...!

Hello,
I am basically an SD consultant. I am not familiar with CRM much.
I have an issue with the Payment Terms in a Sales transaction. It shows different Payment Terms at header and different at item. There is nothing in a Docuemnt's change log. May be user has changed the Peyment Terms is changed while creating Sales Transaction, but the user says he/she had not done so.
This caused a mismatch of Payment Terms at header and item level in R/3 Sales Order and so in Final R/3 Invoice.
What can be the issue..?
As in R/3 the Payment Terms is retrived from the customer master, in CRM also it should be the same as I believe. But I first would like to check the Customer Master (Business Partner) in CRM in Transaction BP. But within Transaction BP where to check the Payment Terms? The Sales Area Data button is there but not active.
Thanks in advance.
Best Regards,
HP

Hi Hardik,
To check the business partner payment temrs, you much change the 'role' of that business partner to, for example, 'sold-to-party' or 'payer'. Then the sales area button will became available so you can check the sales area dependent information, like payment terms.
Can you check?
Kind regards,
Garcia

Customer pricing procedure in Sales transactions

Hello Experts,
In our CRM 2007 we have already customized the pricing procedure of the sales transactions for each sales area / document pricing procedure / customer pricing procedure. But creating sales transactions, our business needs system to take in consideration the customer pricing procedure of the partner in role Ship to party instead of the partner in role Sold to party. Could anybody help telling how to set it?
Many thanks in advance!

well... maybe my question is not clear... the thing is that as a sample, we have a:
1.Sales area = O 50000XXX
2.Sales document type with Pr. Procedure = A
3.SoldTo with Cust Pr. Procedure = 1
4.ShipTo with Cust Pr. Procedure = 2
When we create a sales document, system determines the Pr. Proc. of the doc as it was customized in view CRMV_PRCPROC_DET:
Sales area + Pr. Procedure of the sales doc type + Cust Pr. Procedure = Pr. Procedure of the sales doc
In our customizing we would like to have 2 rows (following the example)
O 50000XXX + A + 1 = ZPROC1
O 50000XXX + A + 2 = ZPROC2
We would need that system checks whether there is any Cust Pr Procedure in the master data of the ShipTo partner.
- If yes, the Pr. Procedure of the sales doc = ZPROC2
- If not, the Pr. Procedure of the sales doc = ZPROC1
but I have not managed to find where to adjust it (nor custom nor BADI). is there any idea or comment?

How to create sales order using BAPI.

Hi all,
I am trying to create sales order using standard BAPI
"BAPI_SALESORDER_CREATEFROMDAT2". But, even I had entered all mandatory fields, I am unable to create sales order sucessfully.
I had gone through the documentaion of this BAPI and entered these fields.
These are the mandatory fields that which I had tried to create,
ORDER_HEADER_IN :
DOC_TYPE Sales document type
SALES_ORG Sales organization
DISTR_CHAN Distribution channel
DIVISION Division
ORDER_PARTNERS..:
PARTN_ROLE Partner role, SP sold-to party
PARTN_NUMB Customer number
ORDER_ITEMS_IN..:
MATERIAL Material number
Do we have anymore fields to give as inputs? I am getting this error message as below :
Msg: Personal number 00007176 does not exit.
But, I am not giving any personal number manually. This personal number was having connection with partner role field,
I had reffered this from the VBPA (Sales Document: Partner Table). Now, please suggest me how to solve this?
Can anyone tell me how to solve this problem and create sales order sucessfully.
Thanks in advance,
Surender Batlanki.

hi surendra ,
chech with below code.
REPORT z_bapi_salesorder_create.
Parameters
Sales document type
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text FOR FIELD p_auart.
PARAMETERS: p_auart TYPE auart OBLIGATORY.
SELECTION-SCREEN END OF LINE.
Sales organization
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text1 FOR FIELD p_vkorg.
PARAMETERS: p_vkorg TYPE vkorg OBLIGATORY.
SELECTION-SCREEN END OF LINE.
Distribution channel
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text2 FOR FIELD p_vtweg.
PARAMETERS: p_vtweg TYPE vtweg OBLIGATORY.
SELECTION-SCREEN END OF LINE.
Division.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text3 FOR FIELD p_spart.
PARAMETERS: p_spart TYPE spart OBLIGATORY.
SELECTION-SCREEN END OF LINE.
SKIP 1.
Sold-to
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text4 FOR FIELD p_sold.
PARAMETERS: p_sold TYPE kunnr OBLIGATORY.
SELECTION-SCREEN END OF LINE.
Ship-to
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text5 FOR FIELD p_ship.
PARAMETERS: p_ship TYPE kunnr OBLIGATORY.
SELECTION-SCREEN END OF LINE.
SKIP 1.
Material
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text6 FOR FIELD p_matnr.
PARAMETERS: p_matnr TYPE matnr   OBLIGATORY.
SELECTION-SCREEN END OF LINE.
Quantity.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text7 FOR FIELD p_menge.
PARAMETERS: p_menge TYPE kwmeng OBLIGATORY.
SELECTION-SCREEN END OF LINE.
Plant
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text9 FOR FIELD p_plant.
PARAMETERS: p_plant TYPE werks_d OBLIGATORY.
SELECTION-SCREEN END OF LINE.
Data declarations.
DATA: v_vbeln            LIKE vbak-vbeln.
DATA: header             LIKE bapisdhead1.
DATA: headerx            LIKE bapisdhead1x.
DATA: item               LIKE bapisditem OCCURS 0 WITH HEADER LINE.
DATA: itemx              LIKE bapisditemx OCCURS 0 WITH HEADER LINE.
DATA: partner            LIKE bapipartnr OCCURS 0 WITH HEADER LINE.
DATA: return             LIKE bapiret2    OCCURS 0 WITH HEADER LINE.
DATA: lt_schedules_inx   TYPE STANDARD TABLE OF bapischdlx
                         WITH HEADER LINE.
DATA: lt_schedules_in    TYPE STANDARD TABLE OF bapischdl
                         WITH HEADER LINE.
Initialization.
INITIALIZATION.
v_text   = 'Order type'.
v_text1 = 'Sales Org'.
v_text2 = 'Distribution channel'.
v_text3 = 'Division'.
v_text4 = 'Sold-to'.
v_text5 = 'Ship-to'.
v_text6 = 'Material'.
v_text7 = 'Quantity'.
v_text9 = 'Plant'.
Start-of-selection.
START-OF-SELECTION.
Header data
Sales document type
header-doc_type = p_auart.
headerx-doc_type = 'X'.
Sales organization
header-sales_org = p_vkorg.
headerx-sales_org = 'X'.
Distribution channel
header-distr_chan = p_vtweg.
headerx-distr_chan = 'X'.
Division
header-division = p_spart.
headerx-division = 'X'.
headerx-updateflag = 'I'.
Partner data
Sold to
partner-partn_role = 'AG'.
partner-partn_numb = p_sold.
APPEND partner.
Ship to
partner-partn_role = 'WE'.
partner-partn_numb = p_ship.
APPEND partner.
ITEM DATA
itemx-updateflag = 'I'.
Line item number.
item-itm_number = '000010'.
itemx-itm_number = 'X'.
Material
item-material = p_matnr.
itemx-material = 'X'.
Plant
item-plant    = p_plant.
itemx-plant   = 'X'.
Quantity
item-target_qty = p_menge.
itemx-target_qty = 'X'.
APPEND item.
APPEND itemx.
Fill schedule lines
lt_schedules_in-itm_number = '000010'.
lt_schedules_in-sched_line = '0001'.
lt_schedules_in-req_qty    = p_menge.
APPEND lt_schedules_in.
Fill schedule line flags
lt_schedules_inx-itm_number = '000010'.
lt_schedules_inx-sched_line = '0001'.
lt_schedules_inx-updateflag = 'X'.
lt_schedules_inx-req_qty     = 'X'.
APPEND lt_schedules_inx.
Call the BAPI to create the sales order.
CALL FUNCTION 'BAPI_SALESDOCU_CREATEFROMDATA1'
       EXPORTING
            sales_header_in     = header
            sales_header_inx    = headerx
       IMPORTING
            salesdocument_ex    = v_vbeln
       TABLES
            return              = return
            sales_items_in      = item
            sales_items_inx     = itemx
            sales_schedules_in = lt_schedules_in
            sales_schedules_inx = lt_schedules_inx
            sales_partners      = partner.
Check the return table.
LOOP AT return WHERE type = 'E' OR type = 'A'.
    EXIT.
ENDLOOP.
IF sy-subrc = 0.
    WRITE: / 'Error in creating document'.
ELSE.
Commit the work.
    COMMIT WORK AND WAIT.
    WRITE: / 'Document ', v_vbeln, ' created'.
ENDIF.
let us know if you have any qauistions.
~linganna

Problem while creating SALES ORDER (OR)

Hi All,
I am unable to create sales order (OR)
Error : Material is not defined for sales areaI have created MMR and CMR Properly.
Please help.
Thanks In Advance
Regards
Abhi

Hi Abhi,
I face similar issue as faced by you.
I went to additional data and changed the description and added the description in which I wanted it to be added but does not help. Am I missing the right place where to make the change?
I am pretty sure that it is a language issue.
I created a sales order, added a product, it worked fine.
Now, I copied this product to a new product, changed description and added it in same sales order it does not work.
Best Regards,
Neha

Create Sales Return Order by BAPI,in pricing manual conditions don't appear

Dear All,
While creating Sales Return Order by using BAPI function module, in pricing manual header conditions are not appearing.
I tried following FMs for creating Sales Return Order. Sales Return Order created but manual header conditions are not appearing.
1.      BAPI_CUSTOMERRETURN_CREATE
2.      BAPI_SALESORDER_CREATEFROMDAT2
3.      SD_SALESDOCUMENT_CREATE
If we create through transaction code u2018VA01u2019 with reference document, manual header conditions are appearing in pricing perfectly.
SAP version is SAP ECC 6.0.
Makarand

Hi there,
Is your return referenced from the F2 invoice or from the riginal order?
If it is from F2 then in VTAF & if it is from OR then in VTAA --> at the item level --> pricing type select the option G copy pricing element unchanged & redetermine taxes or C copy pricing elements & redetermine others. Choose the required option. This is when the same pricing procedure is used in OR & RE order types.
Regards,
Sivanand

Unable to create sales transaction in POSDM though BAPI

Similar Messages

Maybe you are looking for