Sale of used copies of Photoshop

I have upgraded my software to Photoshop 11 and Light room 4, leaving me with copies of PS/ELements 9, 10 with the books. Is it legal to sale the used copies and if it is can the buyer use the same activation codes?

2Trent Roseville wrote:
I have upgraded my software
If you've upgraded then you've still got one license for the software so you cannot sell the old versions.
If you ever want to re-install Elements 11, you'll still need the serial number from one of the older versions in order for your Elements 11 upgrade serial number to be accepted.
If you've bought a new, full version of Elements 11 and Lightroom 4 then, yes, you can sell the older versions provided you transfer the license following these steps
http://helpx.adobe.com/x-productkb/policy-pricing/transfer-product-license.html

Similar Messages

Help Purchasing 4 Copies of Photoshop CS6 with Discs?

Hi All, I am the Team Leader of a very busy medical photography dept at the largest public hospital in New Zealand and we wish to buy 4 new copies of Photoshop CS6 for our medical photogapher ie one for each photographer. We cannot, nor will ever, use the "Cloud" because of the highly confidential images that we document and distribute for medical records and clinical education. The lease option is not going to work either as every automatic monthly payment from generated from our purchasing dept, costs $30 ontop of what our monthly lease would be to Adobe making this too expensive( to say nothing of the inconvienience of being disconnected if a software payment gets missed one month).
Further, we will be upgrading all our machines from Windows XP to Windows 7 in a few months so this will mean re-installing Photosop CS6 (assuming that we can find someone willing to sell us the discs) after that as well...so for lots of reasons the best solution for us at the moment, would be to purchase legacy discs of Photoshop CS6( including Bridge) and I have secured trust funds to purchase this new software.I thought that I could buy 4 legacy versions from either B&H photo in New York or Amazon( who both show legacy discs for sale on their respective websites) but neither will sell these discs to any one outside of the USA.
I have searched for licenced resellers in New Zealand via the Adobe website but none come up. I have tried ringing Adobe New Zealand( 5 times!) but they refuse to return my call even after leaving 5 messages and when I ring the customer support I get put through to a call centre in India where the support consists of an operator with very little English language skills. The one time I did get hold of a native English speaking customer support person in the USA they told me that I had to ring the UK to speak to a person there but the UK is 12 hours behind us so that would mean ringing them in the middle of the night to speak to speak to someone about this ....by now I hope you are getting a very small idea of my frustration with this process and appalling customer service!...can anyone help me please???
Regards Mark Forster-King

I think you are misunderstanding a few things about Creative Cloud
The software is installed on your computer and the data never goes on the cloud unless you specifically choose to put it there.
You mention four copies, but one photographer. Each license allows two simultanious activations of Photoshop. Other people would not need Photoshop to view the images of course.
Your Creative Cloud subscription will NOT stop working if you are unable to log on to the internet for some weeks, (or even months if you have a years subscription).
You can pay for a full year in one go.
Other things to consider:
As a medical department, you would probably want to use the measurment tools that come with the Extended version. That makes CS6 a lot more expensive, but is an integral part of CC
There are some important features being added to CC that I can see your department making good use of.
Creative Cloud has a Teams option, although don't forget you can have two installations for each licence so long as both are used by the same person (deskop and laptop for instance)
I live in Marlborough, and I used to hate the permenent license model because of Adobe's price gouging. It used to cost me around 50% more for Photoshop than people using the same program bought in America. I am paying about NZ$23 a month for a Full Creative Cloud subscription of >30 applications. That is almost exactly the same as in America. Note this is the discounted first year price because I am a previous user, and it goes up to US$50 a month after that first year.
If you are able to qualify for the Photoshop Photographers bundle deal, you will get Photoshop CC and Lightroom for US$10 per month. That is such a bargain.
So all in all, I would advise you to think again about a Creative Cloud subscription.
I am in NZ and would happy to talk to you, although I am not in any way working for Adobe, and would not be able to help regards account details.

Cost of sales flow in COPA and its detailed breakdown cost component f

Hi ,
we have a requirement that we need details about what makes cost of sales numbers in COPA.
i know the our VPRS value is flowing into COPA as COGS but now we want that we should have ite detailed breakdown as per cost components.
can you please tell me detailed configuration steps to make this happen so that we can create a new COPA ke30 report which gives us the breakdown of the COGS numbers.
one more requirement is that for purchase parts our client is maintaing price PB00 condition and some other conditions like brokerage, freight etc in the info record for those materials and they want that all these conditions value should add up to show the COGS value for these purchase parts in the COPA report.. how do we do that?
please reply soon...
Thanks in advance,
Gurjit

Hi Balaji
Which cost elements are you talking about? You can directly make FI postings to COPA in F-02 by clicking on "Prf Seg"
Note that a cost element will either be posted to COPA or Cost Center or Internal order or WBS element... Real posting happens only to one of these...
Out of these, some Cost Centers merge into COGM/COGS i.e. Std cost and this is reflected as COGS.... The variance is posted as variance in COPA
Some cost centers like Marketing which do not form part of COGM/COGS, can be allocated from CO to COPA using KEU5...
This is how the values flow to COPA
Regards
Ajay M

Cost of sales, SD and COPA

Hi everybody
I'm using cost based COPA, and I would like generate the cost of sales posting to COPA from the material document of post goods issue. Does anyone know how to do this?
(I know that the usual way is to use price condition VPRS, but that generates some consistency problems between COPA and FI).
Thanks in advance
JPT

Thank you for your input Ram.
The thing is, I've configured OKB9 so that the COGS account would be filled in with the segment. The problem is that, even tough the segment is filled in the material document, there's no COPA document created. If I create a similar document directly in FI, it creates a COPA document.
I'm also thinking about an alternative solution:
- When posting goods issue, I would post to a "unbilled goods issue" account;
- In the invoice, I would create a new pricing condition that would take the VPRS value would post to the cost of sales account and would clear the "unbilled goods issue" account.
For this second solution I would need additional customizing, exits and pricing routines, but I think it would work. The first solution would be far more simple (basically I would have the same consistency as in account-based COPA, and the additional functionality of cost-based accounting).
If someone has any previous experiences or inputs on these ideas, they would be largely appreciated.
Thanks!
JPT

Sales Analysis in COPA

Hi,
To my understanding data from fields Customer Groups 1-5 and Condition Group 1-5 get copied to sales orders and invoices for sales analysis.
My question is that does the data have to be copied into a sales order and invoice for SALES ANALYSIS or can it be done using different fields such as ATTRIBUTES 1-10 for SALES ANALYSIS in COPA.
Thanks

What fields do you want to come up in the sales analysis report?
My question is that does the data have to be copied into a sales order and invoice for SALES ANALYSIS
Do you mean doing so in ECC..?

Re: Transfer of sales quantity to COPA

Dear CO guys
I have activated CO based COPA and i am transferring sales orders to PA using Record A.
I wish to transfer sales quantity in the sales order to COPA and unfortunately this particular field is not getting transferred.
But i could transfer billed qty in the billing document to COPA
Please let me know how to achieve this
Thanks and Regards
Subbu

Hi,
Good evening and greetings,
There is a standard field for Sales Quantity and it would get transferred if the Sale Order is linked to a Production Order as it would get billed for sure...if it is a normal sales order it will not get transferred...Please go through the following OSS Note
Note 111309 - INFO: Transfer of quantities into CO-PA
Please reward points if found useful
Thanking you
With kindest regards
Ramesh Padmanabhan

How to set the Description Name of Sales Employee in COPA

Dear Expert,
I maintained Characteristis Sales Employee at COPA but when I run this report, there is no description name of employee appear. It just appear the Number of Sales Employee.
I used table VBPA and field Name PARVW in Characteristic Derivation. In Sales Document I created Partner Functin VE Sales Employee.for characterristic and I ser VE Partner Function in SD Document.
In Data Structure KMVTNR Sales Employee there is no Validation Check Table.
Kindly help to solve this problem and thank you in advance for your help.
Cyrenia

You need to use Characteristic Derivations for this to work.
In transaction KEDR, maintain a "look-up" and provide your Reference table as VBPA and your target field will be the COPA Characteristic that you defined for the Partner Function Sales Employee.
Select the Characteristics that will allow you to determine the Sales Employee (Partner Function = "VE") and then map the KUNNR field to the COPA Value Field.
This will allow the flow of Sales Employee Values into COPA and hence the description as well.
Hope this helps.
Cheers.

Characteristic Name of Sales Employee in COPA report is not appear

Characteristic Name of Sales Employee in COPA report is not appear, it is just the a Code of Sales Employee
1.I created Characteristic Derivation t.code KEDR Table lookup PA0001 using condition Origin GLOBAL USERTEMP1 until USERTEMP6
2.During Test Analyze Derivation there was result Derivation was not carried out. Reason: Not fulfilled in Field USERTEMP6
How to solve this problem?
Thanks & Regards,
Cyrenia

You need to use Characteristic Derivations for this to work.
In transaction KEDR, maintain a "look-up" and provide your Reference table as VBPA and your target field will be the COPA Characteristic that you defined for the Partner Function Sales Employee.
Select the Characteristics that will allow you to determine the Sales Employee (Partner Function = "VE") and then map the KUNNR field to the COPA Value Field.
This will allow the flow of Sales Employee Values into COPA and hence the description as well.
Hope this helps.
Cheers.

Error while posting to Tax Journal Entry for sales and use tax

Hi,
I am trying to post a journal entry (FB50) to cleanup and correct the liability on our sales and use tax. All lines are giving warnings and messages.Give me a suggestion on how to get it to post . Or if needed, another solution to correcting the balances in the sales and use taxes.
But the entry to a/c # 226530 is giving an information message but still wouldnu2019t save.
The Error message is
Enter the tax base amounts for account 226400 in company codeAFCO
Message no. F5A375
Diagnosis
You are posting directly to a tax account. Enter the tax base amounts per item using the function "Tax Amounts".
Kindly help me how to fix the above issue.
Thanks
Suvarna

You may want to check out the following notes... they may shed some light on your problem.
681930 - Posting on tax account possible w/o specific. of base amount
1090096 - FB60 / MIRO - Checking direct tax after change (F5A375)
944978 - FB60 / MIRO - check of direct tax after change

Issue in creating sales order using BAPI's...?

Hi Guru's,
i had generated the sales order using the BAPI..but could please guide me how to declare the data declaratin same fields as globally and how to move internal table and how to append ....
thanks in advance...
REPORT z_bapi_salesorder_create.
Sales document type
PARAMETERS: p_auart TYPE auart OBLIGATORY.
Sales organization
PARAMETERS: p_vkorg TYPE vkorg OBLIGATORY.
Distribution channel
PARAMETERS: p_vtweg TYPE vtweg OBLIGATORY.
Division.
PARAMETERS: p_spart TYPE spart OBLIGATORY.
Sold-to
PARAMETERS: p_sold TYPE kunnr OBLIGATORY.
Ship-to
PARAMETERS: p_ship TYPE kunnr OBLIGATORY.
Material
PARAMETERS: p_matnr TYPE matnr   OBLIGATORY.
Quantity.
PARAMETERS: p_menge TYPE kwmeng OBLIGATORY.
Plant
PARAMETERS: p_plant TYPE werks_d OBLIGATORY.
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.
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.
     call FUNCTION 'BAPI_TRANSACTION_COMMIT'.
    WRITE: / 'Document ', v_vbeln, ' created'.
ENDIF.

*& Report ZAREPAS30
REPORT zarepas30.
DATA : gs_vbeln                   TYPE vbak-vbeln,
       gs_order_header_in         TYPE bapisdhd1,
       gs_order_header_inx        TYPE bapisdhd1x,
       gt_order_items_in          TYPE STANDARD TABLE OF bapisditm,
       gwa_itab1                  TYPE bapisditm,
       gt_order_items_inx         TYPE STANDARD TABLE OF bapisditmx,
       gwa_itab2                  TYPE bapisditmx,
       gt_order_partners          TYPE STANDARD TABLE OF bapiparnr,
       gwa_itab3                  TYPE bapiparnr,
       gt_return                  TYPE STANDARD TABLE OF bapiret2,
       gwa_itab4                  TYPE bapiret2.
Sales document type
PARAMETERS: p_auart TYPE auart OBLIGATORY.
Sales organization
PARAMETERS: p_vkorg TYPE vkorg OBLIGATORY.
Distribution channel
PARAMETERS: p_vtweg TYPE vtweg OBLIGATORY.
Division.
PARAMETERS: p_spart TYPE spart OBLIGATORY.
Requested Delivery Date
PARAMETERS: p_edatu TYPE edatu OBLIGATORY.
Sold-to
PARAMETERS: p_sold TYPE kunnr OBLIGATORY.
Ship-to
PARAMETERS: p_ship TYPE kunnr OBLIGATORY.
Material
PARAMETERS: p_matnr TYPE matnr   OBLIGATORY.
Quantity.
PARAMETERS: p_menge TYPE kwmeng OBLIGATORY.
Plant
PARAMETERS: p_plant TYPE werks_d OBLIGATORY.
Start-of-selection.
START-OF-SELECTION.
Header data
Sales document type
gs_order_header_in-doc_type = p_auart.
gs_order_header_inx-doc_type = 'X'.
Sales organization
gs_order_header_in-sales_org = p_vkorg.
gs_order_header_inx-sales_org = 'X'.
Distribution channel
gs_order_header_in-distr_chan = p_vtweg.
gs_order_header_inx-distr_chan = 'X'.
Division
gs_order_header_in-division = p_spart.
gs_order_header_inx-division = 'X'.
Reguested Delivery Date
gs_order_header_in-req_date_h = p_edatu.
gs_order_header_inx-req_date_h = 'X'.
gs_order_header_inx-updateflag = 'I'.
Partner data
Sold to
gwa_itab3-partn_role = 'AG'.
gwa_itab3-partn_numb = p_sold.
APPEND gwa_itab3 TO gt_order_partners .
ship to
gwa_itab3-partn_role = 'WE'.
gwa_itab3-partn_numb = p_ship.
APPEND gwa_itab3 TO gt_order_partners .
ITEM DATA
gwa_itab2-updateflag = 'I'.
Line item number.
gwa_itab1-itm_number = '000010'.
gwa_itab2-itm_number = 'X'.
Material
gwa_itab1-material = p_matnr.
gwa_itab2-material = 'X'.
Plant
gwa_itab1-plant    = p_plant.
gwa_itab2-plant   = 'X'.
Quantity
gwa_itab1-target_qty = p_menge.
gwa_itab2-target_qty = 'X'.
APPEND gwa_itab1 TO gt_order_items_in.
APPEND gwa_itab2 TO gt_order_items_inx.
Line item number.
gwa_itab1-itm_number = '000020'.
gwa_itab2-itm_number = 'X'.
Material
gwa_itab1-material = p_matnr.
gwa_itab2-material = 'X'.
Plant
gwa_itab1-plant    = p_plant.
gwa_itab2-plant   = 'X'.
Quantity
gwa_itab1-target_qty = p_menge.
gwa_itab2-target_qty = 'X'.
APPEND gwa_itab1 TO gt_order_items_in.
APPEND gwa_itab2 TO gt_order_items_inx.
CALL FUNCTION 'BAPI_SALESORDER_CREATEFROMDAT2'
EXPORTING
    order_header_in               = gs_order_header_in
    ORDER_HEADER_INX              = gs_order_header_inx
IMPORTING
    SALESDOCUMENT                 = gs_vbeln
tables
    RETURN                        = gt_return
    ORDER_ITEMS_IN                = gt_order_items_in
    ORDER_ITEMS_INX               = gt_order_items_inx
    order_partners                = gt_order_partners.
Check the return table.
LOOP AT gt_return into gwa_itab4 WHERE type = 'E' OR type = 'A'.
    EXIT.
ENDLOOP.
IF sy-subrc = 0.
    WRITE: / 'Error occured while creating sales order '.
ELSE.
Commit the work.
CALL FUNCTION 'BAPI_TRANSACTION_ROLLBACK'.
    CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.
    WRITE: / 'Document ', gs_vbeln, ' created'.
ENDIF.

Sales Report for US Sales and Use tax

Hi,
I'm looking for t-code to extract detailed sales report having Gross sales, Exempt sales , Ship to state, Ship to County\ City, Sales Tax collected. If I'm getting this report i can verify what my sales tax software is updating.
When i extract tcode - ZINVLIS i don't get much detail.
Please help me in extracting complete sales detail which can be used for sales and use tax verification process and audit purpose.
Thanks,
Karthik

Hi Karthik,
There is no standard report available as per my knowledge.You may develop Z report to achive your requirment. Check some LIS report can give data (MC01 is transaction where you can check all type of key figure reports)
Regards
Mani Kumar

Create sales order using IBE_Quote_W1_PVT.SUBMITQUOTEWRAPPER

Hi,
I am trying to create an sales order using following api. which creates cart from shopping cart.
SET serveroutput ON
DECLARE
P_API_VERSION_NUMBER NUMBER;
P_INIT_MSG_LIST VARCHAR2(200);
P_COMMIT VARCHAR2(200);
X_RETURN_STATUS VARCHAR2(200);
X_MSG_COUNT NUMBER;
X_MSG_DATA VARCHAR2(200);
P_QUOTE_HEADERID NUMBER;
P_LAST_UPDATE_DATE DATE;
P_SHAREE_NUMBER NUMBER;
P_SHAREE_PARTY_ID NUMBER;
P_SHAREE_ACCOUNT_ID NUMBER;
P_SC_BOOK_FLAG VARCHAR2(200);
P_SC_RESERVE_FLAG VARCHAR2(200);
P_SC_CALCULATE_PRICE VARCHAR2(200);
P_SC_SERVER_ID NUMBER;
P_SC_CC_BY_FAX VARCHAR2(200);
P_CUSTOMER_COMMENTS VARCHAR2(200);
P_REASON_CODE VARCHAR2(200);
P_SALESREP_EMAIL_ID VARCHAR2(200);
P_MINISITE_ID NUMBER;
X_LAST_UPDATE_DATE DATE;
X_ORDER_NUMBER NUMBER;
X_ORDER_HEADER_ID NUMBER;
X_ORDER_REQUEST_ID NUMBER;
X_CONTRACT_ID NUMBER;
X_STATUS VARCHAR2(200);
X_HOLD_FLAG VARCHAR2(200);
BEGIN
P_API_VERSION_NUMBER := 1;
P_INIT_MSG_LIST := FND_API.G_TRUE;
P_COMMIT := FND_API.G_FALSE;
P_QUOTE_HEADERID := 18534;
P_LAST_UPDATE_DATE := to_date('2012-10-01 04:33:45','YYYY-MM-DD HH24:MI:SS');
P_SHAREE_NUMBER := FND_API.G_MISS_NUM ;
P_SHAREE_PARTY_ID := FND_API.G_MISS_NUM ;
P_SHAREE_ACCOUNT_ID := FND_API.G_MISS_NUM ;
P_SC_BOOK_FLAG := FND_API.G_MISS_CHAR;
P_SC_RESERVE_FLAG := FND_API.G_FALSE;
P_SC_CALCULATE_PRICE := FND_API.G_FALSE;
P_SC_SERVER_ID := -1;
P_SC_CC_BY_FAX := FND_API.G_FALSE;
P_CUSTOMER_COMMENTS := FND_API.G_MISS_CHAR;
P_REASON_CODE := FND_API.G_MISS_CHAR;
P_SALESREP_EMAIL_ID := FND_API.G_MISS_CHAR;
P_MINISITE_ID := 10660;
IBE_Quote_W1_PVT.SUBMITQUOTEWRAPPER(
P_API_VERSION_NUMBER => P_API_VERSION_NUMBER,
P_INIT_MSG_LIST => P_INIT_MSG_LIST,
P_COMMIT => P_COMMIT,
X_RETURN_STATUS => X_RETURN_STATUS,
X_MSG_COUNT => X_MSG_COUNT,
X_MSG_DATA => X_MSG_DATA,
P_QUOTE_HEADERID => P_QUOTE_HEADERID,
P_LAST_UPDATE_DATE => P_LAST_UPDATE_DATE,
P_SHAREE_NUMBER => P_SHAREE_NUMBER,
P_SHAREE_PARTY_ID => P_SHAREE_PARTY_ID,
P_SHAREE_ACCOUNT_ID => P_SHAREE_ACCOUNT_ID,
P_SC_BOOK_FLAG => P_SC_BOOK_FLAG,
P_SC_RESERVE_FLAG => P_SC_RESERVE_FLAG,
P_SC_CALCULATE_PRICE => P_SC_CALCULATE_PRICE,
P_SC_SERVER_ID => P_SC_SERVER_ID,
P_SC_CC_BY_FAX => P_SC_CC_BY_FAX,
P_CUSTOMER_COMMENTS => P_CUSTOMER_COMMENTS,
P_REASON_CODE => P_REASON_CODE,
P_SALESREP_EMAIL_ID => P_SALESREP_EMAIL_ID,
P_MINISITE_ID => P_MINISITE_ID,
X_LAST_UPDATE_DATE => X_LAST_UPDATE_DATE,
X_ORDER_NUMBER => X_ORDER_NUMBER,
X_ORDER_HEADER_ID => X_ORDER_HEADER_ID,
X_ORDER_REQUEST_ID => X_ORDER_REQUEST_ID,
X_CONTRACT_ID => X_CONTRACT_ID,
X_STATUS => X_STATUS,
X_HOLD_FLAG => X_HOLD_FLAG
DBMS_OUTPUT.PUT_LINE('X_RETURN_STATUS = ' || X_RETURN_STATUS);
DBMS_OUTPUT.PUT_LINE('X_MSG_COUNT = ' || X_MSG_COUNT);
DBMS_OUTPUT.PUT_LINE('X_MSG_DATA = ' || X_MSG_DATA);
DBMS_OUTPUT.PUT_LINE('X_LAST_UPDATE_DATE = ' || X_LAST_UPDATE_DATE);
DBMS_OUTPUT.PUT_LINE('X_ORDER_NUMBER = ' || X_ORDER_NUMBER);
DBMS_OUTPUT.PUT_LINE('X_ORDER_HEADER_ID = ' || X_ORDER_HEADER_ID);
DBMS_OUTPUT.PUT_LINE('X_ORDER_REQUEST_ID = ' || X_ORDER_REQUEST_ID);
DBMS_OUTPUT.PUT_LINE('X_CONTRACT_ID = ' || X_CONTRACT_ID);
DBMS_OUTPUT.PUT_LINE('X_STATUS = ' || X_STATUS);
DBMS_OUTPUT.PUT_LINE('X_HOLD_FLAG = ' || X_HOLD_FLAG);
END;
When i use this from a OA_HTML jsp the sales order is created . But when i use it from the sql developer
i got following error
X_RETURN_STATUS = E
X_MSG_COUNT = 1
X_MSG_DATA = You do not have access to this cart.
X_LAST_UPDATE_DATE =
X_ORDER_NUMBER = 9.990000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000E+125
X_ORDER_HEADER_ID = 9.990000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000E+125
X_ORDER_REQUEST_ID = 9.990000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000E+125
X_CONTRACT_ID = 9.990000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000E+125
X_STATUS =
I checked logs for both .
For working one log is ie. using jsp
01-OCT-2012:01:24:46 IBE IBE_UTIL.enable_debug_new p_check_profile is N
01-OCT-2012:01:24:46 IBE IBE_UTIL.enable_debug_new p_check_profile is N
01-OCT-2012:01:24:46 IBE Begin validate_user_update10/01/2012:01:24:46
01-OCT-2012:01:24:46 IBE Incoming party_id is 423832
01-OCT-2012:01:24:46 IBE Incoming cust_account_id is 140757
01-OCT-2012:01:24:46 IBE Incoming quote_header_id is 18529
01-OCT-2012:01:24:46 IBE User id obtained from environment is: -1
01-OCT-2012:01:24:46 IBE p_save_type is :6
01-OCT-2012:01:24:46 IBE Entered Validation...T
01-OCT-2012:01:24:46 IBE no sharee number
01-OCT-2012:01:24:46 IBE quote_source_code of cart passed in=IStore Account
01-OCT-2012:01:24:46 IBE In validating Owner flow: 423832,140757 10/01/2012:01:24:46
01-OCT-2012:01:24:46 IBE Validate_user_update: Before Last update date validation,p_last_update_date= 01-10-12
01-OCT-2012:01:24:46 IBE Validate_user_update: Last update date validation START
01-OCT-2012:01:24:46 IBE Validate_user_update: l_last_update_date=
01-OCT-2012:01:24:46 IBE Validate_user_update: p_last_update_date=10/01/2012:00:22:07
01-OCT-2012:01:24:46 IBE Validate_user_update: Last update date validation END
01-OCT-2012:01:24:46 IBE Before calling validate_quote10/01/2012:01:24:46
01-OCT-2012:01:24:46 IBE Begin Validate_quote10/01/2012:01:24:46
01-OCT-2012:01:24:46 IBE Validate_quote: Validation for one-click start
01-OCT-2012:01:24:46 IBE End validate_quote10/01/2012:01:24:46
01-OCT-2012:01:24:46 IBE End validate_user_update10/01/2012:01:24:46
but for the failure it is.
01-OCT-2012:01:20:53 IBE IBE_UTIL.enable_debug_new p_check_profile is N
01-OCT-2012:01:20:53 IBE IBE_UTIL.enable_debug_new p_check_profile is N
01-OCT-2012:01:20:53 IBE Begin validate_user_update10/01/2012:01:20:53
01-OCT-2012:01:20:53 IBE Incoming party_id is 9.990000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000E+125
01-OCT-2012:01:20:53 IBE Incoming cust_account_id is 9.990000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000E+125
01-OCT-2012:01:20:53 IBE Incoming quote_header_id is 18529
01-OCT-2012:01:20:53 IBE User id obtained from environment is: -1
01-OCT-2012:01:20:53 IBE p_save_type is :6
01-OCT-2012:01:20:53 IBE Entered Validation...T
01-OCT-2012:01:20:53 IBE no sharee number
01-OCT-2012:01:20:53 IBE quote_source_code of cart passed in=IStore Account
01-OCT-2012:01:20:53 IBE Owner flow with env. userid: 10/01/2012:01:20:53
01-OCT-2012:01:20:53 IBE partyId::quotehdrId(9.990000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000E+125,18529)
01-OCT-2012:01:20:53 IBE End:Expected exception:IBE_Quote_Misc_pvt.validate_user_update
From this u can see that party id and account is fetched when using jsp. but direct running of procedure not getting these values.
is there sql api running when accessing through jsp . so that these values are got from session.
Thanks
Mark

Hi,
I have passed that too . still getting same error.
IBE_Quote_W1_PVT.SUBMITQUOTEWRAPPER calls IBE_Quote_Checkout_Pvt.submitQuote
which calls another package
PROCEDURE Validate_User_Update(
p_api_version_number IN NUMBER := 1.0
,p_init_msg_list IN VARCHAR2 := FND_API.G_FALSE
,p_quote_header_id IN NUMBER
,p_party_id IN NUMBER := FND_API.G_MISS_NUM
,p_cust_account_id IN NUMBER := FND_API.G_MISS_NUM
,p_quote_retrieval_number IN NUMBER := FND_API.G_MISS_NUM
,p_validate_user IN VARCHAR2 := FND_API.G_FALSE
,p_privilege_type_code IN VARCHAR2 := 'F'
,p_save_type IN NUMBER := FND_API.G_MISS_NUM
,p_last_update_date IN DATE := FND_API.G_MISS_DATE
,x_return_status OUT NOCOPY VARCHAR2
,x_msg_count OUT NOCOPY NUMBER
,x_msg_data OUT NOCOPY VARCHAR2)
in it like this
IBE_Quote_Misc_pvt.Validate_User_Update(
     p_init_msg_list => FND_API.G_TRUE
     ,p_quote_header_id => p_quote_Header_Id
     ,p_quote_retrieval_number => p_sharee_number
     ,p_validate_user     => FND_API.G_TRUE
     ,p_privilege_type_code => 'A'
,p_save_type => PLACE_ORDER
,p_last_update_date => p_last_update_date
,x_return_status => x_return_status
,x_msg_count => x_msg_count
,x_msg_data => x_msg_data
from this u can see that there no value passed for party id and account id .
Thanks
Mark

Sale Order Item Quantity Not Populating When Create A Sale Order Using BAPI

I am having a problem when creating a sale order using BAPI
BAPI_SALESORDER_CREATEFROMDAT2
Problem is that sale order item quantity field is not populating
code is as follows
ORDER_ITEMS_IN-ITM_NUMBER = '0010'.
ORDER_ITEMS_IN-MATERIAL = '000000000010000262'.
ORDER_ITEMS_IN-TARGET_QU = 'LB'.
ORDER_ITEMS_IN-TARGET_QTY = 1.

Hi,
Try populating ORDER_SCHEDULES_IN table in the bapi field REQ_QTY.
Regds,
Rudra

Problem regarding the creation of sales order using bapi.

Hai all,
I am creating sales order using bapi but i am, get following error messages :
TYPE ID NUMBER MESSAGE
E       VP   112       Please enter sold-to party or ship-to party
E       V4   219       Sales document was not changed
I have entered all the parameters.
my program is as follows :
*& Report ZSD_SALES_ORDER
REPORT ZSD_SALES_ORDER.
    Tables
*table definitions
TABLES:vbak,      "Sales Document: Header Data
        knvv,     "Customer Master Sales Data
        mara,     "General Material Data
        t001l,    "Plants/Branches
        mvke,     "Sales Data for Material
        vbap,     "Sales Document: Item Data
        konv.     "Conditions (Transaction Data)
    Types
*type for upload data
TYPES :BEGIN OF ty_upload,
       matnr(20) TYPE c,                  " Old material number
       quantity(20) TYPE c,               " Cumulative order quantity in sales units
VALUE TYPE       BAPIKWERT1,
      value(20) TYPE c,                  " Condition value
             value TYPE konv-kwert,                  " Condition value
END OF ty_upload.
*type for final output table
TYPES :BEGIN OF ty_main,
           bismt TYPE mara-bismt,    "Old material number
           matnr TYPE vbap-matnr,    "Material Number
           kunnr TYPE vbak-kunnr,    "customer number
           auart TYPE vbak-auart,    "Sales Document Type
           vkorg TYPE vbak-vkorg,    "Sales Organization
           vtweg TYPE vbak-vtweg,    "Distribution Channel
           spart TYPE vbak-spart,    "Division
           vbeln TYPE vbak-vbeln,    "Sales document
           werks TYPE marc-werks,    " Plant
           lgort TYPE mard-lgort,    "Storage Location
           posnr TYPE vbap-posnr,    "Sales Document Item
           parvw TYPE vbpa-parvw,    "Partner function
           kwmeng TYPE vbap-kwmeng,   "Cumulative order quantity in sales units
           kschl TYPE konv-kschl,    "Condition type
          kwert TYPE konv-kwert,    "Condition value
KWERT TYPE       BAPIKWERT1,
          kwert(20) TYPE c,    "Condition value
           waers TYPE konv-waers,    "Currency
     END OF ty_main.
*type for old material number
TYPES: BEGIN OF ty_matnr,
       matnr TYPE mara-matnr,
       bismt TYPE mara-bismt,
       END OF ty_matnr.
*type for order number
TYPES :BEGIN OF ty_output,
       vbeln TYPE vbak-vbeln,       "Sales Document
     END OF ty_output.
    Constants                Begin with C_                           *
CONSTANTS:
c_zpmu(4) TYPE c VALUE 'ZPMU',
c_zpmm(4) TYPE c VALUE 'ZPMM'.
DATA: c_ch(1) TYPE c VALUE 'X'.
    Data                     Begin with W_                           *
*global data for validations
DATA: w_count TYPE i,
      w_vkorg TYPE vbak-vkorg,
      w_vtweg TYPE vbak-vtweg,
      w_spart TYPE vbak-spart,
      w_werks TYPE t001l-werks,
      w_check TYPE c,
      w_itemno TYPE posnr_va,
     W_COND TYPE C.
      w_cond(3) TYPE c.
    Internal tables          Begin with IT_                          *
*internal table definitions
DATA : it_upload TYPE STANDARD TABLE OF ty_upload ,
       wa_upload TYPE ty_upload.
DATA : it_main TYPE STANDARD TABLE OF ty_main,
       wa_main TYPE ty_main.
DATA: it_matnr TYPE STANDARD TABLE OF ty_matnr,
      wa_matnr TYPE ty_matnr.
DATA : it_output TYPE STANDARD TABLE OF ty_output.
Internal table for BAPI.
DATA: it_bapisdhd1 TYPE STANDARD TABLE OF bapisdhd1,        "Sales and Distribution Document Header
      wa_bapisdhd1 TYPE bapisdhd1.
DATA: it_bapisditm TYPE STANDARD TABLE OF bapisditm ,       "Sales and Distribution Document Item
      wa_bapisditm TYPE bapisditm.
DATA: it_bapiparnr TYPE STANDARD TABLE OF bapiparnr,        "SD Document Partner: WWW
      wa_bapiparnr TYPE bapiparnr.
DATA: it_bapischdl TYPE STANDARD TABLE OF bapischdl,       "Schedule Lines
      wa_bapischdl TYPE bapischdl.
DATA: it_bapicond TYPE STANDARD TABLE OF bapicond,       "Communication Fields for Maintaining Conditions in the Order
      wa_bapicond TYPE bapicond.
DATA: it_bapiret2 TYPE STANDARD TABLE OF bapiret2,        "Return Parameter
      wa_bapiret2 TYPE bapiret2.
      Parameters              Begin with PR_                        *
*selection screen definition
SELECTION-SCREEN BEGIN OF BLOCK blk1 WITH FRAME .
PARAMETERS: pr_vkorg TYPE vbak-vkorg OBLIGATORY,
            pr_vtweg TYPE vbak-vtweg OBLIGATORY,
            pr_spart TYPE vbak-spart OBLIGATORY,
            pr_kunnr TYPE kna1-kunnr OBLIGATORY,
            pr_werks TYPE marc-werks OBLIGATORY,
            pr_lgort TYPE mard-lgort OBLIGATORY.
PARAMETERS: pr_auart TYPE vbak-auart OBLIGATORY,
           PR_AUGRU TYPE VBAK-AUGRU OBLIGATORY.
                        pr_augru TYPE vbak-augru.
SELECTION-SCREEN END OF BLOCK blk1.
SELECTION-SCREEN BEGIN OF BLOCK blk2 WITH FRAME.
PARAMETERS : pr_file TYPE ibipparms-path OBLIGATORY.
SELECTION-SCREEN END OF BLOCK blk2.
      At selection-screen                                           *
AT SELECTION-SCREEN.
PERFORM f006_validate_vkorg.
PERFORM f007_validate_vtweg.
PERFORM f008_validate_spart.
PERFORM f009_validate_kunnr.
PERFORM f010_validate_werks.
PERFORM f011_validate_lgort.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR pr_file.
*for f4 help----
PERFORM f003_f4_help.
      S T A R T   O F   S E L E C T I O N                           *
START-OF-SELECTION.
*for material ,quantity and value upload
PERFORM f001_upload_file.
*get data
PERFORM f003_get_data.
*for check the data
PERFORM f002_check_data .
PERFORM f004_process.
*for posting
PERFORM f005_posting.
END-OF-SELECTION.
      E N D       O F   S E L E C T I O N                           *
*&      Form f001_upload_file
      upload file
FORM f001_upload_file .
DATA : lw_fname TYPE string.
CLEAR lw_fname.
lw_fname = pr_file.
REFRESH it_upload.
CALL FUNCTION 'GUI_UPLOAD'
    EXPORTING
      filename                = lw_fname
      filetype                = 'ASC'
      has_field_separator     = c_ch
    TABLES
      data_tab                = it_upload
    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.
ENDIF.
LOOP AT it_upload INTO wa_upload.
   wa_upload-value = ( wa_upload-value ) / 10.
   MODIFY it_upload FROM wa_upload.
ENDLOOP.
ENDFORM.                    "F001_UPLOAD_FILE
*&      Form f003_f4_help
      f4 help
FORM f003_f4_help .
CALL FUNCTION 'F4_FILENAME'
    EXPORTING
      program_name = syst-cprog
      dynpro_number = syst-dynnr
      field_name    = ' '
    IMPORTING
      file_name     = pr_file.
ENDFORM.                    " f003_f4_help
*&      Form check_data
      text
FORM f002_check_data .
DATA: lw_lines TYPE i.
DESCRIBE TABLE it_main LINES lw_lines.
IF lw_lines LE 0.
    RETURN.
ENDIF.
SELECT a~matnr
         a~bismt FROM mara AS a INNER JOIN mvke AS b
               ON amatnr = bmatnr
               INTO CORRESPONDING FIELDS OF TABLE it_matnr
               FOR ALL ENTRIES IN it_main
               WHERE a~bismt = it_main-bismt.
IF sy-subrc = 0.
    LOOP AT it_main INTO wa_main.
      CLEAR : wa_matnr.
      READ TABLE it_matnr INTO wa_matnr WITH KEY bismt = wa_main-bismt.
      IF sy-subrc = 0.
        MOVE: wa_matnr-matnr TO wa_main-matnr.
      ENDIF.
      MODIFY it_main FROM wa_main TRANSPORTING matnr WHERE bismt = wa_main-bismt.
    ENDLOOP.
ELSE.
   MESSAGE e000(zmsd) WITH text-001.
ENDIF.
ENDFORM.                    "CHECK_DATA
*&      Form F009_validate_vkorg
      text
FORM f006_validate_vkorg .
CLEAR w_vkorg.
SELECT SINGLE vkorg
      INTO w_vkorg FROM tvko
      WHERE vkorg EQ pr_vkorg.
IF sy-subrc <> 0.
    MESSAGE e000(zmsd) WITH text-012 pr_vkorg.
ENDIF.
ENDFORM.                    " F009_validate_vkorg
*&      Form f007_validate_vtweg
      text
FORM f007_validate_vtweg .
CLEAR:w_vtweg.
SELECT SINGLE vtweg
       INTO w_vtweg FROM tvtw
       WHERE vtweg EQ pr_vtweg.
IF sy-subrc <> 0.
    MESSAGE e089(zmsd).
ENDIF.
ENDFORM.                    " f007_validate_vtweg
*&      Form f008_validate_spart
      text
FORM f008_validate_spart .
CLEAR:w_spart.
SELECT SINGLE spart
        INTO w_spart FROM tspa
        WHERE spart EQ pr_spart.
IF sy-subrc <> 0.
    MESSAGE e087(zmsd).
ENDIF.
ENDFORM.                    " f008_validate_spart
*&      Form F010_validate_kunnr
      text
FORM f009_validate_kunnr .
DATA: l_kunnr TYPE kunnr.
CLEAR: w_vkorg, w_vtweg,w_spart.
SELECT SINGLE kunnr FROM knvv
         INTO l_kunnr
         WHERE kunnr = pr_kunnr
         AND    vkorg = pr_vkorg
         AND    vtweg = pr_vtweg
         AND    spart = pr_spart.
IF sy-subrc <> 0.
   MESSAGE e000(zmsd) WITH text-010 pr_kunnr text-011 pr_vkorg .
ENDIF.
ENDFORM.                    " F010_validate_kunnr
*&      Form f010_validate_werks
      text
FORM f010_validate_werks .
CLEAR:w_werks.
SELECT SINGLE werks
        INTO w_werks FROM t001w
        WHERE werks EQ pr_werks.
IF sy-subrc <> 0.
    MESSAGE e088(zmsd).
ENDIF.
ENDFORM.                    " f010_validate_werks
*&      Form F011_validate_lgort
      text
FORM f011_validate_lgort .
CLEAR:w_werks .
SELECT   SINGLE werks FROM t001l
         INTO w_werks
         WHERE werks = pr_werks
         AND    lgort = pr_lgort.
IF sy-subrc <> 0.
    MESSAGE e000(zmsd) WITH text-007 pr_lgort text-008 pr_werks .
ENDIF.
ENDFORM.                    " F011_validate_lgort
*&      Form f003_get_data
      text
FORM f003_get_data .
CLEAR wa_main.
REFRESH it_main.
LOOP AT it_upload INTO wa_upload.
    CLEAR : wa_main.
    MOVE: wa_upload-matnr     TO wa_main-bismt,
          wa_upload-quantity TO wa_main-kwmeng,
          wa_upload-value     TO wa_main-kwert,
          pr_vkorg            TO wa_main-vkorg,
          pr_vtweg            TO wa_main-vtweg,
          pr_spart            TO wa_main-spart,
          pr_kunnr            TO wa_main-kunnr,
          pr_werks            TO wa_main-werks,
          pr_lgort            TO wa_main-lgort.
    APPEND wa_main TO it_main.
ENDLOOP.
ENDFORM.                    " f003_get_data
*&      Form f004_process
      text
FORM f004_process .
CLEAR w_check.
LOOP AT it_main INTO wa_main.
   IF wa_main-matnr = ''.
     WRITE:/ text-006,
                 wa_main-bismt.
     w_check = 1.
   ENDIF.
   IF wa_main-kwmeng = 0.
     WRITE:/ text-005,
             wa_main-bismt.
     w_check = 1.
   ENDIF.
   IF    pr_auart <> 'ZM01'.
     IF wa_main-kwert IS INITIAL.
       WRITE:/ text-004,
                wa_main-bismt.
       w_check = 1.
     ENDIF.
   ENDIF.
ENDLOOP.
ENDFORM.                    " f004_process
*&      Form f005_posting
      text
FORM f005_posting .
CLEAR: w_itemno,
         w_cond.
w_itemno = 10.
w_cond = 1.
IF w_check = '' OR w_check = 1.
wa_bapisdhd1-doc_type = pr_auart.
wa_bapisdhd1-ord_reason = pr_augru.
LOOP AT it_main INTO wa_main.
    IF w_cond = 1.
      CLEAR: it_bapiret2,
             it_bapisditm,
             it_bapiparnr,
             it_bapischdl,
             it_bapicond.
      REFRESH:it_bapiret2,
              it_bapisditm,
              it_bapiparnr,
              it_bapischdl,
              it_bapicond.
      MOVE: wa_main-vkorg TO wa_bapisdhd1-sales_org,
            wa_main-vtweg TO wa_bapisdhd1-distr_chan,
            wa_main-spart TO wa_bapisdhd1-division.
      wa_bapisdhd1-wbs_eleM = 'Y561.1'.
      CALL FUNCTION 'CONVERSION_EXIT_ALPHA_OUTPUT'
        EXPORTING
          INPUT         = pr_kunnr
       IMPORTING
         OUTPUT        = pr_kunnr.
      wa_bapisdhd1-PURCH_NO_S = pr_kunnr.
      wa_bapisdhd1-PURCH_NO_C = pr_kunnr.
    ENDIF.
    MOVE: w_itemno TO wa_bapisditm-itm_number,
           wa_main-matnr TO wa_bapisditm-material,
          wa_main-BISMT TO wa_bapisditm-material,
          wa_main-werks TO wa_bapisditm-plant,
          wa_main-lgort TO wa_bapisditm-store_loc.
                       wa_bapisditm-target_qty = '10'.
    wa_bapisditm-PURCH_NO_S = pr_kunnr.
    wa_bapisditm-PURCH_NO_C = pr_kunnr.
    APPEND wa_bapisditm TO it_bapisditm.
    IF w_cond = 1.
      wa_bapiparnr-partn_numb = pr_kunnr.
      wa_bapiparnr-itm_number = 10.
        wa_bapiparnr-partn_role = 'SP'.
      APPEND wa_bapiparnr TO it_bapiparnr.
      wa_bapiparnr-partn_role = 'AG'.
      APPEND wa_bapiparnr TO it_bapiparnr.
      CLEAR wa_bapiparnr-partn_role.
               wa_bapiparnr-partn_numb = pr_kunnr.
      wa_bapiparnr-partn_role = 'RE'.
      APPEND wa_bapiparnr TO it_bapiparnr.
      CLEAR wa_bapiparnr-partn_role.
               wa_bapiparnr-partn_numb = pr_kunnr.
      wa_bapiparnr-partn_role = 'RG'.
      APPEND wa_bapiparnr TO it_bapiparnr.
      CLEAR wa_bapiparnr-partn_role.
               wa_bapiparnr-partn_numb = pr_kunnr.
      wa_bapiparnr-partn_role = 'WE'.
      APPEND wa_bapiparnr TO it_bapiparnr.
    ENDIF.
    wa_bapischdl-itm_number = w_itemno.
    wa_bapischdl-req_qty    = wa_main-kwmeng.
     wa_bapischdl-PURCH_NO_S = pr_kunnr.
    APPEND wa_bapischdl TO it_bapischdl.
    wa_bapicond-itm_number = w_itemno.
    wa_bapicond-cond_type = 'ZECL'.
     IF    ( wa_bapisdhd1-doc_type = 'ZPMU' ) OR ( wa_bapisdhd1-doc_type = 'ZPMM' ).
       wa_bapicond-cond_type = 'ZVAL'.
     ELSE.
       wa_bapicond-cond_type = 'ZMRP'.       "+PK12122006
     ENDIF.
    wa_bapicond-cond_value = wa_main-kwert.
    APPEND wa_bapicond TO it_bapicond.
    w_itemno = w_itemno + 10.
    w_cond   = w_cond + 1.
ENDLOOP.
data : SALESDOCUMENTIN like BAPIVBELN-VBELN.
CALL FUNCTION 'BAPI_SALESORDER_CREATEFROMDAT2'
    EXPORTING
      order_header_in     = wa_bapisdhd1
    IMPORTING
      salesdocument       = SALESDOCUMENTIN
    TABLES
      return              = it_bapiret2
      order_items_in      = it_bapisditm
      order_partners      = it_bapiparnr
      order_schedules_in = it_bapischdl
      order_conditions_in = it_bapicond.
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
    EXPORTING
      wait = c_ch.
ENDIF.
LOOP AT it_bapiret2 INTO wa_bapiret2.
    DATA : w_err(100) TYPE c,
    w_matnr TYPE matnr.
    IF wa_bapiret2-type = 'E' AND wa_bapiret2-id = 'V1' AND wa_bapiret2-number = 392.
      UNPACK wa_bapiret2-message_v1 TO w_matnr.
      READ TABLE it_matnr INTO wa_matnr WITH KEY matnr = w_matnr.
      IF sy-subrc EQ 0.
        CONCATENATE text-013 wa_matnr-bismt INTO w_err SEPARATED BY space.
        MESSAGE w_err TYPE 'S'.
      ENDIF.
    ENDIF.
    IF WA_BAPIRET2-TYPE = 'S'. " Comment
      WRITE: 40 TEXT-009, WA_BAPIRET2-MESSAGE_V2+0(10).
    ENDIF.
ENDLOOP.
ENDFORM.                    " f005_posting
I have given all the necessary parameters. it is telling that error is in parameter
sales_header_in.
I have checked it.
i have assigned purch_no_s and purch_no_c of the structure BAPISDHD1(ORDER_HEADER_IN)
in the bapi with customer number.
and also i have assigned the partnumber of the structure BAPIPARNR ORDER_PARTNERS
in the bapi with customer number.
but still , it is diplaying the error message, please enter the sold to or ship to party number.
how to resolve this error.
this is urgent requirement.
points will be awarded.
thanking u in advance,
a.srinivas.

Hi,
Did u have a look at the standard programs which make use of BAPI_SALESORDER_CREATEFROMDAT1
Heres a list...
LWSSOU08
MV45WF0S
MWWMJF21_BAPI_SALESORDER_CREAT
RBUS2032
Regards,
Tanveer.
<b>Please mark helpful answers</b>

Problem while creating sales order using BAPI

Hi all,
i am creating a sales order from the purchase order data.
when my client will send a PO in EDI format, my 3rd party edi tool will convert that edi formatted PO to text format. then i will upload that text formatted PO to my program then i will create a SO from those uploaded PO data using BAPI BAPI_SALESORDER_CREATEFROMDAT2.
but,no sales order is being created.& also i am not getting any return message.by debugging also, i am not getting the error.plz suggest where i am doing mistake.below is the coding.
DATA:
gfilename LIKE rlgrap-filename.
*--Internal tables
DATA: BEGIN OF i_item OCCURS 50.    "Create Material Document Item
        INCLUDE STRUCTURE BAPISDITM .
DATA: END OF i_item .
DATA: BEGIN OF i_partner OCCURS 20. "Return parameter
        INCLUDE STRUCTURE BAPIPARNR.
DATA: END OF i_partner.
DATA: BEGIN OF i_schedule OCCURS 20. "Return parameter
        INCLUDE STRUCTURE BAPISCHDL .
DATA: END OF i_schedule.
DATA: BEGIN OF i_cond OCCURS 20. "Return parameter
        INCLUDE STRUCTURE BAPICOND .
DATA: END OF i_cond.
DATA: BEGIN OF i_part OCCURS 0,     " Internal table for split data
        part(20),
      END OF i_part.
DATA: BEGIN OF i_return OCCURS 20. "Return parameter
        INCLUDE STRUCTURE bapiret2.
DATA: END OF i_return.
*-- Work areas
DATA: BEGIN OF wa_header .       "sales Document Header Data
        INCLUDE STRUCTURE BAPISDHD1.
DATA: END OF wa_header .
*DATA: BEGIN OF wa_return .       "Output Structure
       INCLUDE STRUCTURE BAPIRET2.
*DATA: END OF wa_return .
DATA: begin of sorder.
     INCLUDE STRUCTURE BAPIVBELN.
DATA: end of sorder.
data:begin of t_upload,
     ebeln(10), "PO no(seagate)
     aedat like sy-datum , "PO date
     bsart(4) , "PO type
     vdatu like sy-datum , "requested delivery date
     kunnr(10) , "customer no-sold-to-party
    kunak like vbak-kunnr, "bill-to-party
     name1_s(20), "name1 of sold-to-party
     name2_s(15), "name2 of sold-to-party
     land1_s(3), "country
     ort01_s(10), "city
     regio_s(3), "region(state/province)
     pstlz_s(10), "postal code
     adrnr_s(10), "address
     bstkd_e(10), "end customer purchase order
     posex(6),     "end customer PO line no(item no)
     kdmat(18),     "end customer material no(part no)
     kunag(10),     "ship-to-party
     name1_c(20),   "name1 of ship-to-party
     name2_c(15),   "name2 of ship-to-party
     land1_c(3),   "country
     ort01_c(10),    "city
     regio_c(3),   "region(state/province)
     pstlz_c(10),   "postal code
     adrnr_c(10),   "address
     posnr(6), "item no(seagate PO line no)
     pstyv(4), "item category
     matnr(18), "material no(seagate 9 digit part no)
     zmeng(13), "Target quantity in sales unit
    vrkme like vbap-vrkme, "sales unit
     meins(3), "UOM
    posnr_tot like vbap-posnr,"Total no. of line items
     werks(4), "plant
    vstel like vbap-vstel, "shipping point
     empst(10), "receiving point
     shtyp(4), "shipment type
     route(6), "route
     vsbed(2), "shipping conds
    rkfkf like vbap-rkfkf, "method of billing for co/ppc orders
     zterm(4), "terms of payment key
     inco1(3), "F.O.B inco term1
     inco2(3), "F.O.B inco term2
     end of t_upload.
Data: wa_upload like t_upload,
       i_upload like standard table of t_upload.
Data:v_kunnr like kna1-kunnr,
      v_posnr like vbap-posnr,
      v_matnr like vbap-matnr,
      v_zmeng like vbap-zmeng,
      v_kunag like kna1-kunnr.
*---Constants
CONSTANTS: c_comma TYPE c VALUE ',',   " For splitting data at commas
           c_01(2) TYPE c VALUE '01', " For movement code in Bapi
           c_b     TYPE c VALUE 'B',   " For mvt. Indicator in Bapi
           c_creat(5) TYPE c VALUE 'CREAT', " For button text
           c_clear(5) TYPE c VALUE 'CLEAR', " For clear button
           c_mvmt(4) TYPE c VALUE 'MVMT',
           c_ok(2)   TYPE c VALUE 'OK',
           c_error(5) TYPE c VALUE 'Error'.
*--SELECTION SCREEN DESIGN--
SELECTION-SCREEN BEGIN OF BLOCK blk1 WITH FRAME.
PARAMETERS:
            p_auart LIKE vbak-auart, " order type
            p_vkorg LIKE vbak-vkorg, " sales org
            p_vtweg LIKE vbak-vtweg, " dist channel
            p_spart LIKE vbak-spart, " division
            p_vkgrp LIKE vbak-vkgrp, " sales group
            p_vkbur LIKE vbak-vkbur, "sales office
            p_file(256) default 'c:/saleorder.txt'.         "File name
SELECTION-SCREEN END OF BLOCK blk1.
SELECTION-SCREEN PUSHBUTTON 15(10) v_create USER-COMMAND creat.
SELECTION-SCREEN PUSHBUTTON 40(10) v_clear USER-COMMAND clear.
INITIALIZATION -
INITIALIZATION.
v_create = c_creat .
v_clear = c_clear.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_file.
PERFORM selectfile USING p_file.
*--AT SELECTION_SCREEN--
AT SELECTION-SCREEN .
IF sy-ucomm = c_clear.
    PERFORM f_clear.
ELSE.
   IF sy-ucomm <> c_mvmt.
**--- Validating the input data.
     PERFORM f_check_inputs.
    ELSEif sy-ucomm = c_creat.
*--- Validating the input data.
      PERFORM f_check_inputs.
*-- Uploading the PO data.
      PERFORM f_PO_upload.
*---checking the PO data
     PERFORM f_check_upload_data.
*---create sales order from PO data
    PERFORM f_Sales_order_create.
    ENDIF.
FORM f_PO_upload.
gfilename = p_file.
CALL FUNCTION 'WS_UPLOAD'
       EXPORTING
            filename                = gfilename
            filetype                = 'DAT'
       TABLES
            data_tab                = i_upload
       EXCEPTIONS
            conversion_error        = 1
            file_open_error         = 2
            file_read_error         = 3
            invalid_type            = 4
            no_batch                = 5
            unknown_error           = 6
            invalid_table_width     = 7
            gui_refuse_filetransfer = 8
            customer_error          = 9
            OTHERS                  = 10.
IF sy-subrc <> 0.
    MESSAGE i398(00) WITH '(WS_UPLOAD)'
    ' Errors occured with exception '
     sy-subrc.
ENDIF.
ENDFORM.                    " f_PO_upload
*&      Form selectfile
      text
     -->P_P_FILE text
FORM selectfile CHANGING value(filename) TYPE c.
CALL FUNCTION 'WS_FILENAME_GET'
       EXPORTING
            def_filename     = gfilename
            def_path         = 'C:\'
            mask             = ',*.txt.'
            mode             = 'O'
            title            = 'Select File Name'
       IMPORTING
            filename         = filename
       EXCEPTIONS
            inv_winsys       = 1
            no_batch         = 2
            selection_cancel = 3
            selection_error = 4
            OTHERS           = 5.
ENDFORM.                    " selectfile
FORM f_Sales_order_create.
PERFORM f_fill_header.
PERFORM f_fill_partner.
PERFORM f_fill_item.
PERFORM f_call_BAPI.
ENDFORM.                    " f_Sales_order_create
*&      Form f_fill_header
      text
--> p1        text
<-- p2        text
FORM f_fill_header.
move p_auart to wa_header-doc_type.
move p_vkorg to wa_header-sales_org.
move p_vtweg to wa_header-distr_chan.
move p_spart to wa_header-division.
move p_vkgrp to wa_header-sales_grp.
move p_vkbur to wa_header-sales_off.
Read table i_upload into wa_upload index 1.
move wa_upload-ebeln to wa_header-purch_no_c.
move wa_upload-aedat to wa_header-purch_date.
move wa_upload-bsart to wa_header-po_method.
move wa_upload-vdatu to wa_header-req_date_h.
move wa_upload-bstkd_e to wa_header-purch_no_s.
*move wa_upload-route to wa_header-route.
move wa_upload-vsbed to wa_header-ship_cond.
move wa_upload-empst to wa_header-rec_point.
move wa_upload-shtyp to wa_header-ship_type.
move wa_upload-zterm to wa_header-pmnttrms.
move wa_upload-inco1 to wa_header-incoterms1.
move wa_upload-inco2 to wa_header-incoterms2.
ENDFORM.                    " f_fill_header
*&      Form f_fill_partner
      text
--> p1        text
<-- p2        text
FORM f_fill_partner.
if not wa_upload-kunnr is initial.
select single kunnr from kna1 into v_kunnr
            where kunnr = wa_upload-kunnr.
if sy-subrc <> 0.
Message E014 with 'customer does not exist'.
else.
move 'AG' to i_partner-partn_role.
move wa_upload-kunnr to i_partner-partn_numb.
move wa_upload-land1_s to i_partner-country.
move wa_upload-name1_s to i_partner-name.
move wa_upload-name2_s to i_partner-name_2.
move wa_upload-ort01_s to i_partner-city.
move wa_upload-regio_s to i_partner-region.
move wa_upload-pstlz_s to i_partner-postl_code.
move wa_upload-adrnr_s to i_partner-address.
append i_partner.
endif.
endif.
if not wa_upload-kunag is initial.
select single kunnr from kna1 into v_kunag
            where kunnr = wa_upload-kunag.
if sy-subrc <> 0.
Message E015 with 'end customer does not exist'.
else.
move 'WE' to i_partner-partn_role.
move wa_upload-kunag to i_partner-partn_numb.
move wa_upload-land1_c to i_partner-country.
move wa_upload-name1_c to i_partner-name.
move wa_upload-name2_c to i_partner-name_2.
move wa_upload-ort01_c to i_partner-city.
move wa_upload-regio_c to i_partner-region.
move wa_upload-pstlz_c to i_partner-postl_code.
move wa_upload-adrnr_c to i_partner-address.
append i_partner.
endif.
endif.
ENDFORM.                    " f_fill_partner
*&      Form f_fill_item
      text
--> p1        text
<-- p2        text
FORM f_fill_item.
loop at i_upload into wa_upload.
if not wa_upload-matnr is initial.
select single maramatnr msegmenge into (v_matnr, v_zmeng) from
                   mara inner join mseg on maramatnr = msegmatnr
                   where mara~matnr = wa_upload-matnr.
if sy-subrc <> 0.
Message E016 with 'material no does not exist'.
elseif v_zmeng LT wa_upload-zmeng.
Message E017 with 'order quantity is greater than the quantity present'.
endif.
endif.
move wa_upload-posnr to i_item-itm_number.
move wa_upload-pstyv to i_item-item_categ.
move wa_upload-matnr to i_item-material.
move wa_upload-zmeng to i_item-target_qty.
move wa_upload-meins to i_item-target_qu.
move wa_upload-werks to i_item-plant.
*move wa_upload-meins to wa_vbap-meins.
*move wa_upload-posnr_tot to wa_vbap-posnr_tot.
move wa_upload-posex to i_item-po_itm_no.
move wa_upload-kdmat to i_item-cust_mat22.
move wa_upload-inco1 to i_item-incoterms1.
move wa_upload-inco2 to i_item-incoterms2.
move wa_upload-zterm to i_item-pmnttrms.
move wa_upload-empst to i_item-rec_point.
move wa_upload-shtyp to i_item-ship_type.
move wa_upload-route to i_item-route.
append i_item.
PERFORM f_fill_schedule_line.
PERFORM f_fill_conditions.
ENDLOOP.
ENDFORM.                    " f_fill_item
*&      Form f_fill_schedule_line
      text
--> p1        text
<-- p2        text
FORM f_fill_schedule_line.
move wa_upload-matnr to i_schedule-itm_number.
move sy-datum to i_schedule-req_date.
move wa_upload-zmeng to i_schedule-req_qty.
append i_schedule.
ENDFORM.                    " f_fill_schedule_line
*&      Form f_fill_conditions
      text
--> p1        text
<-- p2        text
FORM f_fill_conditions.
move wa_upload-matnr to i_cond-itm_number.
move sy-datum to i_cond-conpricdat.
append i_cond.
ENDFORM.                    " f_fill_conditions
*&      Form f_clear
      text
--> p1        text
<-- p2        text
FORM f_clear.
clear:p_auart,
      p_vkorg,
      p_vtweg,
      p_spart,
      p_vkgrp,
      p_vkbur.
ENDFORM.                    " f_clear
*&      Form f_call_BAPI
      text
--> p1        text
<-- p2        text
FORM f_call_BAPI.
clear:i_item,i_partner,i_schedule.
CALL FUNCTION 'BAPI_SALESORDER_CREATEFROMDAT2'
EXPORTING
SALESDOCUMENTIN               =
    ORDER_HEADER_IN               = wa_header
ORDER_HEADER_INX              =
SENDER                        =
BINARY_RELATIONSHIPTYPE       =
INT_NUMBER_ASSIGNMENT         =
BEHAVE_WHEN_ERROR             =
LOGIC_SWITCH                  =
TESTRUN                       =
CONVERT                       = ' '
IMPORTING
   SALESDOCUMENT                  = sorder
TABLES
RETURN                        =
   ORDER_ITEMS_IN                 = i_item
ORDER_ITEMS_INX               =
    ORDER_PARTNERS                = i_partner
   ORDER_SCHEDULES_IN             = i_schedule
ORDER_SCHEDULES_INX           =
ORDER_CONDITIONS_IN            = i_cond.
ORDER_CFGS_REF                =
ORDER_CFGS_INST               =
ORDER_CFGS_PART_OF            =
ORDER_CFGS_VALUE              =
ORDER_CFGS_BLOB               =
ORDER_CFGS_VK                 =
ORDER_CFGS_REFINST            =
ORDER_CCARD                   =
ORDER_TEXT                    =
ORDER_KEYS                    =
EXTENSIONIN                   =
PARTNERADDRESSES              =
if not ( sorder-vbeln is initial ).
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.
write: /'Order number:', sorder.
else.
loop at i_return.
write: / i_return-id, i_return-number, i_return-message(80).
endloop.
*write: /'Error'.
endif.
*loop at i_return.
*write: / i_return-id, i_return-number, i_return-message(80).
*endloop.
ENDFORM.                    " f_call_BAPI

HI
Pricing will be carried basing on the pricing
procedure.
Case1: Prices will be carried out automatically if
necessary condition records are maintained for the
condition type.
For this you can go to Sales Order-> Item Conditions
In the screen you can click on command button Analysis,
which gives you the list of condition types associated
to the pricing procedure. By clicking on the condition
type you can know the action that has taken place.
Case2: Manually forcing prices for Items.
To do this, you have to populate ORDER_CONDITIONS_IN &
ORDER_CONDITIONS_INX. Also note to identify the item
numbers, you manually pass the item number for each item
in the sales order, use the same item number for
populating conditions.
Parameters required:
ORDER_CONDITIONS_IN:
ITM_NUMBER, COND_TYPE, COND_VALUE, CURRENCY
ORDER_CONDITIONS_INX:
ITM_NUMBER, COND_TYPE, UPDATEFLAG, COND_VALUE,CURRENCY.
   Hope the above info helps you. Do revert back if you
need more info.
Kind Regards
Eswar

Sale of used copies of Photoshop

Similar Messages

Maybe you are looking for