Sales orders with rejection reason in R3 are not nullified in BW

Hi,
Actaully One sales order xs26665 has been uploaded into BW from R/3 with OrderQty 100
After cancellation of same order xs26665 in R/3 by putting Rejection Reason, R3 extractor is generating two records as specified
1st record specifies order xs26665 with Order Qty = -100
2nd record specifies oredr xs26665 with Order Qty = 100 and updating filed "reason for rejection" = EQ.
Because of this two records which are generated in R3 after cancellation which are loaded in to BW, The value of Order Qty for sales order xs26665 is not geting nullified and it still shows final value which is = 100 as order qty.
This records is first geting uploaded in to ODS and further in to a cube in BW using deltas.
Rgds,
C.V.
Message was edited by:
C.V. P

Hi CVP,
make sure that the datasource that you are extracting the data from has got the field ROCANCEL and that the keyfield Quantity is marked or checked in the column Inversion.,.. (3rd field in your datasource... Selection Hide Inversion & Field Only).. There check the Inversion box for your Quantity field... only on enabling this would your Quantity in BW get negated... The cancelled order would then be marked as 'X' for the field ROCANCEL which inturn would be picked up by the BW through the InfoObject 0STORNO..
Hope it solves your issue...
Regards
Manick

Similar Messages

Sales Order Credit Account and Credit control area not updated

Hi,
I have a production issue. I have two sales orders created from Same Value contract, with same PO, same sold to party same payer. Both the orders created by same user at the same time.
First SO has credit control area and credit account is updated but the second order did not update with this information.
For first order, if I go to Environment -> Partner -> Display credit account, system taking to FD33 screen of the credit account.
For the second order, above menu path giving message "Cannot display credit limit as no credit management account is available"
Please let me know how fix the second order to rectify this issue.
Thanks,
Satish

Hi,
Goto OVAK T.Code.
Assign credit check to your second sales order type.
Assign the values from "A" to "D".Any value as per your need.
Save.
Regards,
Krishna.

Cancel a Sales order with a PP order

Hi
I want to cancel a sales order that has a production order assoiced with it . the production order has status REL Released
MSPT Material shortage
PRT Printed
PRC Pre-costed
GMPS Goods movement posted
RESA Results analysis carried
SETC Settlement rule created
The order dose not have any varent dollars assocated with it and the conformation has been removed
I can not cancel the sales order

Hello,
As the production order is associated with the sales order, it may not allow you to cancel/delete the sales order.
TECO the production order, set deletion flag, if the production order is not to be used. After this reject the sales order with a Reason for Rejection or delete the sales order.
Prase

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

Create EDI sales order with reason for rejection set for item

Hello all,
I'm trying create an EDI sales order with item rejected, but I get the following error: Item 000001's configuration can no longer be changed.
I set the reason for rejection in the segment E1EDP01, field ABGRU.
How can create the sales order, with item rejected without error?

Use program SDJEDI to simulate the error (see note 380603)
This way you can figure out whether the same issue exists in VA01 or just in the SD EDI process
From reading the issue, it seems you have a configurable item and the line is not open for input and that's why your reason for rejection is ignored.
But SDJEDI should tell you everything.
Run it first to see the BDCDATA your idoc produces.
Then run it again in simulate mode and it should take you very close to the error
Hope this helps
Paul

List of rejected sales order with quantity and value

Hi,
Is it possible to get the report from VA05 for the list of rejected items with value and quantity ?
Pls help
Thanks,
Vijesh

Dear Vijesh,
VA05 I believe is a very powerful report for doing analysis at order and line item level. If your rejection criterion includes a rejection reason at line item level, yes this list from VA05 can give rejected Sales Orders with Quantity and Value. See the screen shot below.
I selected a list with open dates till date, I can see Sales Order number, Sales Document Type, Item Number, Material, Rejection reason, Quantity at line item level and net price.
However, I am not sure what is the rejection criterion you use in your business and I am not sure if you use rejection reason and hence I would like to hear from you, if this explanation helps you.
Thanks
Nagaraj

Creation of sales order with reference - Zfields in Add data B are not cop

Hi all,
Please help me in the issue . I am creating sales order with reference to returns order . All item fields are getting copied but the Zfields which are added in addtional data b of sales order are not getting copied. Can anyone please let me know the procedure to copy the custom fields.
Thanks in advance,

The setting of field when copy by reference is best done in the copy rules.
If you go to transaction VTAA, and look to the order type you are copying to, you will find a data transfer rule number.
Then go to transaction VOFM, menu option DATA TRANSFER -> ORDERS and find the matching data transfer rule number.
Select and press the "Source text" button, here you will find the data from the copied order in structure CVBAK, and you can apply the code to set the VBAK structure fields appropriately.
This should then populate the data on the copied order.

Creating Sales Order with reference to Quotation from different Sales Area

Hi,
I would like to inform you that our customer (GE ENERGY OC) from Europe have a requirement where they want to create sales orders with reference to quotation that is from different sales area. Standard SAP functionality doesn't allow this feature, hence requesting your help to give me an update in this regard.
Please treat this as urgent as they have to do business cutover where they are in the process of completing open sales orders.
Thanks
Ashfaq
Mobile: +91-98857-07558
E-Mail: [email protected]

Hi RadhaKrishna,
In standard system it is not possible to create sales order from a quotation whose sales are is different.
However I think this is possible by using some user exit in sales order. I have never tried this.
Regards
srini

Sales order with refernce to contracts in different sales area

Hi Gurus,
I am creating a sales order with reference to a contract.I am making sales order sold-to-party as release order.
so my Contract sold-to-party and the sales order sold-to-party are different but both belong to same sales area. In the above case i am able to create sales order.
In other case though my Contract sold-to-party and the sales order sold-to-party are different but if they both belong to different sales area, i am unable to create a sales order.It says no contracts exits for sold-to-party.
i made both the customers as partners .
<POINTS OFFER REMOVED BY MODERATOR>.

Hi,
Could you please let us know why are you opening multiple threads in different forums for the same question?
You have already created another thread in ABAP General
creating sales order with reference to contracts
Please refrain from using "Any guidance on this is fully rewarded with points."
Please read the rules of engagement before posting.
Posting multiple threads for same question in different/same forums and making point offers are not encouraged on the forum.
Thank you

Sales orders with # signs

When you're posting sales order documents to the system, normally would you make sure the # signs are not saved with the data field entries?
How do the # signs get there or are these normal?
I would think the description texts or any texts would allow special characters but what if it is something that describes a material number or something else, would you allow # signs for these fields?

If you read my message more detail, it saids that the value are characteristics of the material numbers; essentially they are attributes and you would say that you would want to order these material numbers with these attributes. And the master data attributes do not have the # signs from tcode CT04 but displayed from VA03.
I am not talking about texts here either. That's obvious.
Theorectically, I am saying that SAP should have some mechanisms if it does not already. It checks if something doesn't exist within the F4 dropdown if you enter some other value, it will display a message that it doesn't exist or something for that field, but for some reason some fields are not checked.
Again, # signs were not entered from CT04 but are displayed from VA03.

Error while creating sales order with ref to contract

while creating sales order, with refernce to contract system is giving a message
Configuration not possible for material : Reason 3 --> Help
Message no. V1360
and the message is as follwed can any one explain
Diagnosis
This may have been caused by one of the following:
1. The configuration profile for the material allows or requires the bill of materials to be exploded during order processing. However, a plant has not been specified in the item.
2. The configuration profile of the material allows or requires the bill of materials to be exploded during order processing, but the order quantity in the item must be greater than 0.
3. A configuration profile has not been maintained
or
A configuration is not permitted for the material
or
4. The configuration profile of the material allows or requires the bill ofmaterials to be exploded during order processing. However, the system could not determine a date because important data is missing from the item (see incompletion log).

Hi
I think you have both Variant configuration and BOM.
Pls ensure the following.
1. BOM masterdata is maintained for the variants
2. Variant configuration is configured correctly
Configuration profile is created for the material
Knowledge base object and run time version are available
3. Maintain materials as not relevant for delivery or dont give delivery quantity as 0
Once you are sure that these are in proper shape, you can start creating order. The problem wont come.
Reward points if it helps you.

Sales order with reference to sales order

Hi,
 I need to create a sales order with reference another sales order using bapi CreateFromDat2. Please note, Sales Ord. Dist. channel, Div, sold-to to of the new order are different from original order. I gave reference order in field order_header_in-REFDOCTYPE . I am getting following error when I perform single test " FB Call: insufficient parameters. Can any of you tell me how to overcome this issue. And is it possible to create an order refering to another Saler order with different Sales Ord, Dist. channel, Division, sold-to ?
<REMOVED BY MODERATOR>
Cheers
Sudhaker
Message was edited by:
 Alvaro Tejada Galindo

There is an OSS note <a href="https://service.sap.com/sap/support/notes/370988">Note 370988 - BAPIs in SD: Creation with reference</a>
Symptom
This note describes the problems of the 'Create with reference' function when using BAPIs to create sales documents.
If you are working online, you can use this function module to create a sales document with reference to an existing sales document or a billing document (for example, a debit or credit memo request) according to fixed rules. The rules for transferring information from the source document to the target document are defined in the copying control on header and item level. The creation with reference permits an item selection.
When you use BAPIs in SD, a function of this type is not fully available. A reference is only possible for a quantity contract, so that the target quantity of the contract can be reduced by the order quantity of the sales document. Furthermore, the document flow is also updated.
As an alternative to 'Create with reference' in Transaction VA01, two variants are provided for solving the 'Create with reference' problem in the BAPI.
 1. Create a '1:1 ' - that is, a document copy of a sales document (customer quotation, order) with 'BAPI_SALESDOCUMENT_COPY'. At this point, you cannot create the 1:1 copy of either a billing document or a delivery.
 2. Create a sales document that refers to an existing document with 'BAPISDORDER_GETDETAILEDLIST' and 'BAPI_SALESORDER_CREATEFROMDAT2'.
Other terms
BAPI_SALESDOCUMENT_COPY, BAPI_SALESORDER_CHANGE, BAPI_CUSTOMERINQUIRY_CHANGE, BAPI_CUSTOMERQUOTATION_CHANGE, BAPI_SALESORDER_CREATEFROMDAT1, BAPI_SALESORDER_CREATEFROMDAT2, BAPI_SALESORDER_CREATEFROMDATA, BAPISDORDER_GETDETAILEDLIST
Reason and Prerequisites
As of yet, no method exists for creating a sales document that refers to an existing document.
Solution
For solution No. 1
 1. Create the documents using the BAPI_SALESDOCUMENT_COPY function module. However, this only permits a 1:1 copy without factoring out individual items.
 2. After you have created the document copy, you can use a change BAPI to edit this copy.
For solution No. 2
 1. Collect the data for the reference document (for example a customer quotation) with the 'BAPISDORDER_GETDETAILEDLIST' function module. In the example code, focus exclusively on the partners, items, schedule lines and conditions.
 2. Prepare the Data. Execute the 'copying control' manually. This way, you decide which values are to be transferred.
 3. Create the sales document using the 'BAPI_SALESORDER_CREATEFROMDAT2' function module by transferring the prepared data.
 4. Finally, you must remove a COMMIT WORK so that the sales document can be written into the database.
An example of solution 2 is attached as a text file. You are allowed to select items and quantities for example, if you use input parameters. If there are no entries, then transfer 1:1 from the reference document. When you enter the 'condition type' parameter, you can determine whether conditions are copied or recalculated ('G' for transferring from the preceding document; 'B' or ' ' for re-determining, and 'C' for re-determining with transfer of the manual elements).
Sample : <a href="https://websmp108.sap-ag.de/~sapidb/012003146900000486112004E/BAPI_COPY_WITH_REF.txt">ZZ_MS_BAPI_COPY</a>
Regards

Replication of Sales order with Credit Card data from CRM to R/3

Hi,
We are on CRM 4.0 version.
We are getting the sales order management system implemented in CRM 4.0.
Simulation for credit card authorization has been set up CRM system.
When we maintain the credit card in the sales order,the replication does not take place.The outbound Queue in the R/3 system is getting stuck with the error 'VBERROR'.
Can you please advice if we can replicate the sales order with the credit card maintained on them to R/3 system.
thanks
Meraj

Hi Bokhal,
Please consider my answer from your recent thread dealing with apparently the same issue :
Hi Bhokal,
For filters in uploads please consider below:
For Filtering the BP-upload, use the Administration Console
(tx. SMOEAC) in the corresponding subscription of the "All Business
Partners (MESG)" publication assigned to the R/3 site.
Some publications (and the replication objects they are based on) are
delivered as type "Simple bulk" which does not give you the opportunity
to assign criteria values for filtering.
You might have to re-create the publication. To do that:
1) First delete the subscriptions "All Business Partners (MESG)" and its
publications & the replication object.
2) Recreate the replication object as type "Simple intelligent".
3) Afterwards you can create a new publication via wizard of type
"Simple intelligent (msg)" assigned to the BDOC-Type BUPA_MAIN. Then,
you will be able to select some "filter criteria".
The reason for deleting the "old" publication is, that you
are not allowed to assign a BDOC-Type to more than one publication.
4) But please keep in mind that there is no realignment supported. So
you should only use fields for filtering, which cannot be changed
afterwards.
This is the "simple" solution for filtering on fields. This
will not provide complex filter criteria.
If you need this, you shall create a filter function in R/3- and/or
CRM-Inbound and -outbound.
If you want to keep the control about the upload trigger, you can add an
additional module in transaction CRMC_BUT_CALL_FU, position > 200000.
BUPA_MWX_BDOC_BPS_FILL_CENTRAL. Within this new module, you can delete
all partners within the complex structure that you don't want to upload.
Hoping that above will be helpful.
Best regards
Christophe Sturzel

How to create sales order with configuration?

Hi, all!
I'm trying to create sales order with multi-level BOM's explosion using BAPI_SALESORDER_CREATEFROMDAT2, but with no success.
Scanning and following ton's of OSS notes and already posted answers in this forum regarding configuration in sales order doesn't lead to success to.
So can anybody throw light on rules for populating data structures for items and items configuration in case of multi-level BOM's explosion in sales order? Providing working code snippet would be great.
Regards,
Maxim.

Hi, all!
Just want to properly close the thread and share experience gained.
The main reason of error was in incorrect TABLES parameters populating for sales order items and their configuration.
Not the secret that there is a lack of documentation for even BAPIs FM, especially for comprehensive things to do. And it seems that the right way to resolve proper structure of import/tables parameters for "creation/change" function modules is to call "corresponding read-FM" for object created on-line and see how return parameters are populated.
For example, for BAPI_SALESORDER_CREATEFROMDAT2 such corresponding FM is BAPISDORDER_GETDETAILEDLIST, which returns near the same structures.
Actually in my case such algorithm was used in the first place. But BAPISDORDER_GETDETAILEDLIST returned wrong parameters as was discovered later This error was fixed by implementing OSS note 821191 and sales order was succesfully created.
And I want to thank SAP Support experts in effective assistance. 10 points are yours!
Regards,
Maxim.

How settlement rule will be created for Sales order with cost object

Dear Experts,
We are using product cost by sales order with valuated stock. In addition we are not using COPA
We also consume some materials at sales order level and at the end of month we want to do the result analysis and settlement for the same amount. In this case can any on explain how system will behave regarding settlement of sales order cost and what entries will get pass in the system.
In our case we have done below activities...
we have created sales order,
All production order activities completed till final GRN including month end activities
Material consumption against sales order
Result analysis executed
At the time of sales order settlement, system throwing error (Sender doesn't have valid receiver, please create settlement rule for sender object)
Then i checked in sales order there sales order settlement rule not defined.
I guess this settlement rule need be generated by system automatically. If not, please let me know the process of it.

HI kishore
the reason is that sale order always carry the revenue and production order and production period carry the cost .
cost you can settle to the Material and even management want to be settle the cost to material only in production order OR period
but in sales order when u sell the product it carry the revenue not the cost and management want see and analysis based on profitability segment are profit center level .
Prerequisites
If CO-PA is active, the system generates a settlement rule when you create the sales order. The settlement rule determines whether data is settled to other objects or other areas in Controlling. In accordance with this settlement rule, the relevant data is settled to CO-PA.
If CO-PA is not active, create a settlement rule. This settlement rule that you create manually normally contains a G/L account as a receiver (such as 399999). You can also settle costs and revenues or results analysis data to objects with revenue.
You can also settle the cost of sales calculated in results analysis to a fixed asset or a cost center. To do this, you must add to the allocation structure the results analysis cost elements under which the cost of sales is updated to the order.
The settlement rule includes a distribution rule for the sales order item. The distribution rule is made up of a settlement receiver, a settlement share, and a settlement type:
The settlement receiver (such as profitability segment or G/L account) specifies the object to which the actual costs and revenue of the sales order item are settled. The settlement receiver can be proposed through the settlement profile.
The settlement share defines the percentage or the equivalence numbers used to distribute the costs to the individual settlement receivers. The settlement share for sales order items is usually 100%. A settlement share of 100% is preset in the system.
The settlement type specifies full settlement of the sales order item. This ensures that all the data on the sales order is available for results analysis.
Settlement still takes place in each period. The revenues and the cost of sales are transferred to CO-PA by period, and the work in process and the reserves are transferred to FI.

Sales orders with rejection reason in R3 are not nullified in BW

Similar Messages

Maybe you are looking for