Net receivable problem in sales order.

Dear gurus
I have a requirement where client wishes to show the net receivable from the price only. For example right now as is it seems net value is grabbing the value from the total value.
qty                       Net Value 1,010
Example: Pr00 is 1,000
SED                     1%
total Value       1,010
Net Receivable 1,010
VPRS Cost ***
Client wants net value at the top to show as 1,000 based off of the price pr00.
In the pricing procedure the net value assignments as as followed:
Print A, SubTotal A=Carry over price to KOMP-CMPRE (credit price),      ALtCty 4 =Net value + tax, everything else is blank.
Please Help.

Hi
AS per my understanding you can enter the new condition type with below configuration details
Cond. class D Taxes
Calculat.type H Percentage included
Cond.category D Tax
Rounding rule Commercial
StrucCond.
with the above the system will caluculate the tax amount from the total value and shows the net value .
if you have nay further clarifications let me know
Regards
Damu

Similar Messages

I have a problem regarding sales order line item with confimed quanity

Hi Experts,
I have a problem regarding sales order line item with confimed quanity with '0' with delivery block but confirming the sales order quantity once the order is released from credit check.
The situation arises as per the below scenarios.
Scenario - 1 - When the sales order has two line item - one line item with confirmed qunaity in the schedule line and for the 2nd line item there is no available stock for the Material xxxxxx.
Initially the sales order is created for the line item 2 with confirmed quantity = 0, and having the delivery block = 01 for the Material xxxxxx and the order is set with credit check. Once the order is relased from the credit check. The quanity for the item 2 where the confirmed quantity will be = 0 ( Where it is not changing the confirmed quantity)
Scenario -2- Updating the order qunaity for the line item 2 as (9Pcs) it will goes to credit check and save the order.
Maintain the stock for the line item 2 ( 5 Pcs).
Once the order is released from the credit check. Then for the line item 2 the confirm quanity will be seting to 5 Pcs with Delivery blcok 01.
This should not happen, When the credit check is released even though if it has stock based on the delivery blockl it should set the confirmed quanity to Zero.
Can you please help me how to solve this issue.
Looking forward for your reply.
Thanks and Regards,

Hi,
I agree with your point. In the sales order When the complete delivery check box is enabled where the confimed qty is set to zero, it is fine but when we save the orderr it goes to credit check. Once we release the order using VKM3 where in the sales order the confimed quantity is setting to 5, But it should set to Zero quantity. Quatity should not be get confirmed it should be Zero Quantity.
Further in SPRO - customizing in the deliveries blocking reasons - It has a tick mark in the confirmation blcok. But we dont want to remove the - Confirmation Block tick mark
Please any one can help me if you have any solution to solve this problem.
Thanks and Regards.

Condition Period Problem in Sales order - Need help

Hi Gurus
I am testing Sales Order back dated
Condition period Problem in Sales order
example for you to understand
Sales Order where PO date is 17.12.2007
Del Date & Price date is 13.02.2008
Then it is not calculating IN: A/R BED %IN A/R BED totalN A/R CESS [1621]
But if i do it after 14 feb 2008 then it is calculating IN: A/R BED %IN A/R BED totalN A/R CESS [1621]
When I do it with current date it is calculating IN: A/R BED %IN A/R BED totalN A/R CESS [1621] say date is 9-5-2008
I am not able to trace out problem, kindly help me from where I do I check and why this is happening.
Rajesh Chalke

Hi,
I am not sure if this solves your problem, but I am suspecting that this might be due to the 'valid on date' of the condition records created for the relevant duty condition types.
Since it was a recent regulation and VK11 usually defaults current date as the valid date, that condition record may have been valid only from the recent date on which it was created.
Check the date in VK12 (To find the exact selection parameters, check the pricing analysis in the sales order which will display the exact condition record which is being selected as of current date.) Check for the same parameters; change the date to relevant date in the past and recreate the sales order. Hopefully this should solve the issue.
Cheers,
KC

BAPI - Problem in Sales order creation

Hi Friends,
I have problem in Sales order creation using BAPI ,I am getting a messsage - Error in creating document ,I have sent the code along with this mail ,can you help it out.
Code:
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.
Regards,
Dinesh

what messages u are gettting in RETURN ? Please check the RETURN tables data.
[code]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.
Regards
Prabhu

Problem in Sales Order with specific condition type.

Hello Experts,
I'm facing a problem in sales order creation for a specific condition type.
the actual scenario is as below,
We have created a new condition type for special discount.This condtion type is applicable only for specific sales channels.Also the discount percentage has to fetched from a custom table.
To achieve this I've written a user exit "RV64A999"
In the FM, i've calculated the subtotal and fetched the discount percentage and calculated the discount amount. After implementing this, the SO were been created properly. for all the line items the discount amount was getting calculated properly.
But then I added a condition at the top of code in exit that the calculation for the new condition type should happen only for selected sales channels.
But after adding this condition in code, i'm facing problem. Now when I create/ change any SO, the discount amounts are getting calculated incorrectly. I'm getting discount amount even if the line item subtotal amount is zero (0).
Any help or pointers reagrding this issue will be very helpful and highly appreciated.

Hi ..
Check your config. again or debug the routine code with your ABAPer and find the problem area.
-Maharshi

Rounding off value problem in sales order

Hi All,
This is related to a rounding off value problem in sales order.
The problem is described by an example which is as follows -
Selling Price of Material A = Rs. 176.76
Excise charged = Rs. 21.80
Total Price = Rs.176.76 + Rs.21.80 = Rs. 198.56
On this total Trade Discount (ZDTD) having access sequence,is calculated at the rate of 4% = Rs. 7.94
But the condition base value after the discount is showing Rs.198.60 instead of Rs.198.56
I want the system to reflect the value as Rs.198.56 intact and it should not round up to the nearest value i.e. Rs. 198.60
Why is this happening? Is it possible to reflect the exact value? If yes what is needed to be done?
The commercial round off is activated for the DIFF Condition Type.
Looking forward to some valuable suggestions.
Thanks & Regards
Priyanka Mitra

Hi Ramesh,
Thanks for your suggestion but the problem has been solved by me.
Regards
Priyanka Mitra

Problem about sales order stock stock transfer and batch determination

Hi, experts, I get a problem about sales order stock stock transfer and batch determination.The following is the current situation of my system:
In OMCG I assigned search procedure ME0001 to both 311 and 311 E and ticked check batch. After that, I found that if iI need to tranfer unrestricted-use material from storage location 1000 to 2000 with movement type 311, I just need to input * at the field batch, then the system will display all of the available batches. But for the transferring of sales order stock with movement type 311 E, after I input * at the batch field, no batch is displayed and there is also no message from the system.
Can anybody help me? Is there anything else I need to do? Thanks very much.

I think my question is not clear, actually I tried 562 E , 411 E and 413 already. all the transaction looking for the sales order but unfortunatly the sales order is deleted from SAP.

Problem with sales order and Service order

Dear Guru's
We have a real problem with sales orders and service orders and how we treat these. For a project that uses a WBS, it's not a problem to manipulate SAP to give us a list of shortages (orders with no or limited supply) for each order, but for some reason our after sales orders and our service orders do not work this way.
Thanks and Regards,
Deethya.

CLOSED

Net Price of a Sales Order

Hi All,
In standard system the net price of a sales order is given by the condition type PR00. Is it possible to change the source of net price to customer-defined condition type like ZFMA?
Thanks + Best Regards
Jerome

Condition Type: If existing condition type meets the requirement, we need not create a new condition type. Considering the requirement for new condition type, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Condition Type. It is always recommended to copy an existing similar condition type 'PR00' & copy as 'ZMFA'.
General process for configuring pricing procedure:
In SD, Pricing Procedure is determined based on Sales Area (Sales Organization + Distribution Centre + Division) + Customer Pricing Procedure + Document Pricing Procedure. Sales Area is determined in Sales Order Header Level. Customer Pricing Procedure is determined from Customer Master. Document Pricing Procedure is determined from Sales Document Type / Billing Type (if configured). Once the pricing procedure is determined, Condition records are fetched. If appropriate condition records are found, the price is determined. If Mandatory pricing condition is missing, system will through an error message.
In SD, the steps to configure Pricing procedure are as under:Step 1:
Condition table: If existing condition table meets the requirement, we need not create a new condition table. Considering the requirement for new condition table, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Condition Table (select the required fields combination, which will store condition record).
Step 2:
Access Sequence: If existing access sequence meets the requirement, we need not create a new access sequence. Considering the requirement for new sequence, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Access Sequence (Access sequence is made up of Accesses (Tables) & the order of priority in which it is to be accessed. Here we assign the condition table to access sequence.
Step 3:
Condition Type: If existing condition type meets the requirement, we need not create a new condition type. Considering the requirement for new condition type, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Condition Type. It is always recommended to copy an existing similar condition type & make the neccessary changes. Here we assign Access sequence to Condition type.
Step 4:
a. Pricing Procedure: It is recommended to copy a similar pricing procedure & make the neccesary changes in new pricing procedure. Pricing Procedure is a set of condition type & arranged in the sequence in which it has to perform the calculation. Considering the requirement for new Pricing Procedure, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Maintain Pricing Procedure.
b. Pricing Procedure: After maintaining the pricing procedure the next step will be determination of pricing procedure. Configuration for determining pricing procedure in SPRO is as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Determine Pricing Procedure.
Step 5.
Condition record: Condition record is a master data, which is required to be maintained by Core team / person responsible from the client. During new implementation, the condition records can be uploaded using tools like SCAT, LSMW, etc.
It is assumed that document pricing procedure, customer pricing procedure , ... are in place.
Regards,
Rajesh Banka
Reward points if helpful.

The problem for sales order ra settlement

dear friends
i encounter a problem in sales order settlement
1 we use rev based result analyse ,and with profit realization
2 when the so status is rel ,the valuation base is Q,when the status is TECO and finl ,the valuation base is J
3 when we partially do the billing and run the ra settlement ,the poc = cumulate act rev/plan rev * actual cost in current period(i think this should be the cumulate actual cost ),and it lead to the error calcuation of the COGS,i do not know where the confirguation is error ,is in valuation base ?
can you help me
thank you

dear friends
i encounter a problem in sales order settlement
1 we use rev based result analyse ,and with profit realization
2 when the so status is rel ,the valuation base is Q,when the status is TECO and finl ,the valuation base is J
3 when we partially do the billing and run the ra settlement ,the poc = cumulate act rev/plan rev * actual cost in current period(i think this should be the cumulate actual cost ),and it lead to the error calcuation of the COGS,i do not know where the confirguation is error ,is in valuation base ?
can you help me
thank you

Net Value of the Sales Order in Document Currency is Zero

Hi,
I have an issue with Sales order where in "Net Value of the Sales Order in Document Currency" field value in the initial screen is getting displayed as Zero. But in Pricing Conditions tab "Net Value in Document Currency" is showing correct value.
Could someone advice what causes this situation and how to fix it.
Thanks.
Best regards,
srikrishhna13

Hi Navaneeth,
Need your help and advice again. My later investigations reveals the below.
In some Orders (with a different item category) the Net value is getting reflected at Header level, irrespective of whether the line item/items are under some RfR.
My earlier case were with Orders (item category different from above) the Net Value is Zero when all the line items are under some RfR.
Kindly help me how to fix this issue.
Thanks.
Best regards,
Srikrishhna

Regarding receiver category in sales order.

hi Gurus,
I am facing a problem in making Sales Order, the problem is as follows: -
I have enter the all input to make SO, like sold-to-party, division, qty, etc.
But, by cliking enter i got a massage " receiver category is not allowed by SD1 settlement profile"
I check the parameter of receiver category as well as settlement profile, but i can't understand it.
please any one tell me to how to solve this problem?
Thanks in advance,
Regards,
Shripad

Hi
It is some thing to do with settlement profile for the sales order.
you better coordinate with your CO collegue for solvin this.
Regards
YMREDDy

Problem with sales order consumption

Hi
I hope someone can help? I have a problem with consumption of sales orders in APO. When a sales order comes across from R/3 it doesn't consume the forecast until a later sales order comes across, then the previous one consumes forecast. So all sales orders consume forecast apart from the latest one on each material.
Many thanks
Michael

Hi Please confirm the following are right in your strategy configuration in R/3:
Strategy:         40 Planning with final assembly
Reqmts type for indep.reqmts   VSF Planning with final assembly
Reqmts class: 101
Consumption: 1 Consume planning with assembly
Planning Ind.   1 Net requirements planning
Reqmt type of customer reqmt   KSV Sales order with consumption
Requirements class             050 Warehouse consumpt.
Allocation indicat.   1 Consume planning with assembly
No MRP                  Requirement planned

Problem migrating sales orders

Hi all,
I have a problem with the migration of sales orders from one SAP system to other.
Scenario: A SAP system with sales orders and with its own condition types (prices and discounts). The data of sales orders pending for billing have been extracted to excel files and it's going to be transfer to the new system using a custom batch-input. In the new system, I have created a manual condition type ZP99 which it'´ll contain the net value for prices (in KOMV-KWERT) because it has different condition types.
The problem is that I need to keep the unit value (conditional amount) in the field KOMV-KBETR, but when I execute the batch-input, because rounding issues, the value loaded in KOMV-KWERT is modified in the sales order.
E.g.:
Initial values in excel file:
Target quantity = 439
Conditional value = 950,46
Conditional amount is calculated = 950,46/439 = 2,1650569476082004555808656036446 (rounding problem)
After executing batch-input:
Conditional value is modified to = 952,63
Conditional amount will be rounded = 2,17
Please, could you give me some advice to keep initial values?
Thanks in advance.
Edited by: Eduardo Hernandez Nieves on Aug 5, 2009 6:45 PM

Hi,
I have found a solution to my problem: I changed ZP99 to fixed amount (calc type), and I removed the division to obtain the unit price in the batch input. This unit price will be put in a subtotal position.
Thanks.

Free Goods Problem in Sales Order

Hello All,
The problem is related to Free Goods in Sales Order which is given with an example -
We have maintained Free Goods ( T Code - VBN1) in inclusive scenario which is as follows -
For 210 PAC (Pack) of Material A 18 PAC Free.
Where 1 PAC = 20 BT (Bottle) and 20 PAC = 1 CV (Case Pack)
In the material master of Material A the Base Unit Of Measurement (UOM) = PAC and Sales UOM = Blank so that we can use any conversion factor maintained for the material.
The conversion factors maintained for Material A are as follows -
1 BT = 1BT
1 PAC = 20 BT
1 CV = 20 PAC
Now when we are raising sales order for 11 CV the free goods are not generated in the Sale Order.
Again if we maintain the Sales UOM in CV and raise the sales order it is showing :
10 CV as main item and 1 CV as Free which is wrong because in the conversion factor we have already maintained 1CV = 20 PAC , Whereas in the inclusive scenario it is given 11CV = 210 PAC and 210 PAC = 18 PAC is free.So in any case it is taking into account 2 more PACs.
Please suggest what need to be done in this case in respect of SD / ABAP(if needed).
Thanks & Regards
Priyanka Mitra

Yes Priyanka
This is a very interesting and a challenging issue or question
I think because of the prorata calculation type the extra 2 units is coming
This logical error has happened to me too
Inclusive 210 units means we have defined as 192 + 18 in VBN1
But the system determines the free goods in sales order as 190 + 20 that means there are 2 units which are going free than what has been maintained as condition record
But system converts our logic into its own thro that calcultion type PRO RATA which is the main culprit here
So it requires ABAP help
This qn should be awarded points (unfortunately i am not able to do so)
Regards
Raja

Net receivable problem in sales order.

Similar Messages

Maybe you are looking for