Need help in sales order creation

How to create a sales order ,invoice,credit memo
step by step.

Hi,
SD Flow Cycle:
INQUIRY ( VA11)
|
QUOTATION (VA21)
|
PURCHASE ORDER (ME21)
|
ORDER CONFIRMATION (VA01)
|
PICKING LIST (VL36)
|
PACKING LIST - (VL02, VL01)
|
SHIPPING (VT01)
|
INVOICE (VF21, VF01)
|
AR
SALES ORDER PROCESSING
Creating Sales Order - VA01
Maintaining a Sales Order - VA02
Displaying a Sales Order - VA03
Releasing an Order or Delivery from Credit Hold: Non-Flooring - VKM1
Display List of RMAs by Customer - VA05
Confirm RMA Goods Receipt - VL02
Generate list of open return orders for deletion - VA05
Display Customer returns eligibility - MCSI
Removing a Billing Block (Approving Credit/Debit Requests) - V.23
SHIPPING
Creating a Delivery - VL01N
Displaying a Delivery - VL03N
Changing a Delivery - VL02N
Shipment Inquiry / Display - VT03
Adjusting Transfer Order - Confirmation Quantity - LT12
Collectively Confirm Transfer Order - LT25
Batch Shipment Confirmation - VL19
PGI Reversal Cancellation - VL09
Creating Service Provider/Carrier Master Data - XK01
Maintaining Serive Provider/Carrier Master Data - XK02
Displaying Service Provider/Carrier Master Data - XK03
Maintaining Product Master/Serial # Profile/Unit of Measure/Shipping Unit - MM02
IDoc Inquiry - WE02 / WE05
BILLING
Invoicing a Customer Shipment - VF01
Reprinting an Invoice - VF31
Releasing a Sales Order for Billing - V.23
Creating an Invoice by Using the Billing Due List - VF04
Checking Open Billing Documents - VF05
Create Credit/Debit Memo - FB01
Please Reward If Really Helpful,
Thanks and Regards,
Sateesh.Kandula

Similar Messages

Need code for Sales order creation in oops using xi as integration server

Need code for Sales order creation in oops using xi as integration server.

hi rocky,
could you pls give a bit explanation on what you are expecting.
regards,
Pavan

Need help in Sales order Header Details

Hellp Experts,
I need to modify data on 'Additional Info B' in Sales Order Header (VA03 Transaction) . As it is a Standard program I am aware that we have to use user Exits. But before that I have to debug the code to that point. I wish to know info from where a particular data is coming in the field (End User). How should I proceed for debugging? Can anybody help me?
Moderators,
I could n't found any similar question when searcher. If it is can you please provide me the links?
Best Regards,
Harish
Moderator message: debugging is standard developer practice, enhancement of this screen has been discussed many times, it seems you did not look in the right places.
Edited by: Thomas Zloch on Nov 30, 2010 5:48 PM

Hi Harish,
Perhaps have a look at the following thread...
Additional Data B tab blank in VA01
Have a look at some of the includes mentioned in the thread and if you don't find the information there, you should at least be pointed in the right direction.
Kind Regards,
Richard.

Need help on sales order confirmation out put type

Hi Team,
Please help on this issue.
In our sales document types order confirmation is happening through the inboud idoc, user requrement is once order is confirmed immediately sales order confirmation output type should send sucessfully, but the problem is
Inbound idoc is using the sales order and blocking at the same time RSNAST program is using this sales order for sending the output type but not able to send due to the sales order is blocked by inbound idoc.
Could you some body help me on this how can we proceed on this.
thanks & Regards,
MK.

Check the Dispatch time of the Output type in transaction code :NACE. You need not execute RSNAST00, if the despatch time is set to 3 ( Send with application own transaction ) or 4 (Send Immediately). The output will trigger automatically after the sales order is saved.

Need help on Sales Order Strategy Group 20.

Hi PP Gurus,
Could anybody please help me out of this problem?
Strategy group 20 is for purely MTO scenario. I know the execution part including most of the possibilities in PP module but I'm not that much aware regarding Costing part for it. Could anybody please focus somewhat on costing part required for it like
1. Sales order costing only required or Periodic or Order based costing also solve the purpose in general?
2. What will be the impact if we go for Sales Order Costing?
Since we are using here REM environment.
Please come with prompt comments.
Thanks & Regards,
Abu Arbab

Hi,
Since your scenario is MTO, so sale order costing is the most suitable one. It is better to run the sale order costing for each & every sale order. It is similar like the standard cost estimation and EK02 condition type will bring the value in sale order pricing. This condition type you need to define in the requirement class.
regards,
V. Suresh

LSMW - Need help with Sales Order (Modification VA01)

Hi,
I need help with an LSMW for Sales Order (VA01).
I need to do the following:
1. Copy the Standard Sales Order LSMW
2. They (users) would like to be able to pick the batch (lot) from the sales order.
3. Also, they would like to have functionality, where from the list of Sales Order numbers, they would be able to switch one part number for another.
Please help with the above 3 needs.
Thanks,
Laura

Hi
Run transaction SE38, insert your program (RVINVB10), select DOCUMENTATION option and press display
Just only you need to consider the BDC program needs to read afile with all informations to create a sales order, so you have to create a program to prepare a file arraged as RVINVB10 needs, the documentaion explains how the file has to be created.
Max

Need help passing Sales Order header text to PO header texts

I would really appreciate if someone can help me with this. I am able to pass the line item texts using configuration (text linkage) but SAP does not provide a way to pass header level texts to PO. Any help is appreciated.

Message was edited by: B P
Message was edited by: B P
Message was edited by: B P

Need sales order creation using bapi in oops

need code for sales order creation using bapi in oops

hi rocky,
could you pls give a bit explanation on what you are expecting.
regards,
Pavan

Duplicate purchase oredr number message need in sale order creation

Hi,
My requirement is for a user exit for sales order creation.
When user create a sales order and put customer purchase order number based on purchase order number
user entered it will check data base table and if its duplicate entry then throw the error.
So, Requirement is :
1: Give error for duplicate purchase order number.
I need user exit name.
Please help.
Regards,
Moderator Message: Please search before posting basic questions. Thread locked.
Edited by: Neil Gardiner on Apr 29, 2011 9:31 AM

Whether to allow duplicate PO numbers from a customer is a configuration setting.... However, what you're asking seems strange.... what has company code got to do with it, unless you want to allow PO numbers to dupllicate across SAP company codes...e.g., customer orders on PO #1 from company code 001 and PO #1 from company code 002....
Usually, we would want to apply duplicate PO code checking at the customer number level, wouldn't we? If customer 1 sends me PO #1 and customer 100 sends me PO #1, I certainly would want to accept both orders.
Consult your SD functional specialist about configuring this option.

User Exit during Sales Order Creation - New Line Item needed

I have a situation during the process of sales order creation. If a Material in a line item has say 27 EA and the Base Unit is EA. But the Sales Unit is CSE. Then whenever the user enters 27 EA and presses enter he should get two line items.
The first line item needs to convert to maximum number of CSE posible and the rest will be the second line item with the remaining EA. The order isn't important but that is what is needed. Question is how do I approach this problem and code my user exit accordingly and where do I code it.
I was looking at SAPMV45A and saw the program MV45AIZZ which is meant as a user exit for any PAI event handling. If anybody has encountered this kind of requirement can you please share your view on this.
I will definitely reward points for useful answers.
Clark

Hello Mahendra
The requirement is as follows :
PART 1:
Sales Order Enter:
1.     When a line item is entered on a sales order (VA01 or VA02), at enter, check the sales unit of measure (VBAP-VRKME).
     Do not check line items where item category (VBAP-PSTYV) = TANN, TAPS or ZTAP. TANN are free goods that should not be considered for consolidation. TAPS & ZTAP are lower level materials as a result of product selection. They will be attached to a higher-level material with an item category of TAX, which is relevant for consolidation.
     Do not check items where VRKME <> EA
2.     If VRKME = EA, go to MARM for MATNR.
3.     Go to record where alternate unit of measure (MEINH) = CSE, get the value from the numerator field (UMREZ).
4.     Divide the order quantity (VBEP-WMENG) by UMREZ.
5.     If the result is greater than 1.0, the customer has ordered more than one case and a new line item needs to be added to the sales order for the case quantity.
6.     Add a new line to VBAP for the same material with the case quantity. If not a whole value, the remainder of eaches (bottles) should update the qty on the first item on VBAP.
     Part 1 is relevant for order types ZCA, ZOR, ZSO, RE, ZSM
PART 2:
Batch Job to run prior to the Delivery Due List:
1.     Read VBUK for Delivery Status (LFSTK) = A (delivery not processed). Get all of the document numbers (VBELN).
2.     Go to VBEP for those document numbers to get the goods issue date for the order. There will be many records in VBEP for the same sales order. Look at all orders with a goods issue date (WADAT) of next day.
3.     Go to VBAK for those document numbers to see if there are multiple sales orders for the same Sold To party (KUNNR).
4.     For customers who have more than one order in VBAK, search all line items (for all orders). If there are no duplicate materials across sales orders, do nothing.
     Do not check line items where item category (VBAP-PSTYV) = TANN, TAPS or ZTAP. TANN are free goods that should not be considered for consolidation. TAPS & ZTAP are lower level materials as a result of product selection. They will be attached to a higher-level material with an item category of TAX, which is relevant for consolidation.
     Do not check line items where reason for rejection (VBAP-ABGRU) is not blank
5.     If there are duplicate materials, go through the same logic as in part 1. If the quantity across the sales orders adds up to greater than one case, add the appropriate quantity to a new line item on the first sales order.   If there is a remainder qty, update the line item on the first sales order with this qty. In this case, the quantities on the second sales order needs to be closed out with a reason for rejection code of 50, Line Item Consolidation. If there is no remainder, update the qty on this item directly.
     Part 2 is relevant for order types ZOR, ZCA, ZSM
     This batch job will have to be run manually for Day Pick orders. The end of this program should automatically kick off the delivery due list for Day Pick orders, shipping condition 02.
Business Justification:
The business requires that like order line items be consolidated to one line item prior to the order going to the warehouse for picking. This will aid in picking at the warehouse as well as result in the customer invoice not reflecting more than one line item for the same material. In the case where the customer has truly ordered more than a case, i.e;, 1 case, 2 bottles, the documents in SAP will still reflect 2 lines.

Need to fetch sales order no. before creation

Hi Experts,
My requirement is to add text in "Text" tab at item level in Sales Order creation. This is working fine for VA02 as I am using folowing code:
FM to store date in the 'Text' tab of the Sales Order
    CALL FUNCTION 'CREATE_TEXT'
         EXPORTING
              fid         = 'Z0CF'
              flanguage   = gc_spras     "Language
              fname       = gv_so_it        "Sales Order No+Item number
              fobject     = gc_obj
              save_direct = 'X'
              fformat     = '*'
         TABLES
              flines      = it_temp           "Data to populate text tab with
         EXCEPTIONS
              no_init     = 1
              no_save     = 2
              OTHERS      = 3.
    CLEAR it_date.
ENDLOOP.   "it_date
It is working fine for VA02 as SO no. is existing and fname is getting sales order no and item no. to create text.
My problem is that I want to do same thing for transaction VA01. But the problem is fname doesn't get appropriate data as SO is still not created.
Is there any way I can achieve this?
Any structure or table that I can use?
Your help in this regard will be highly appreciated.
Best Regards,
Vishal Sharda.

Hi ,
       Create a Z function module in update task add the code
CALL FUNCTION 'CREATE_TEXT'
EXPORTING
fid = 'Z0CF'
flanguage = gc_spras "Language
fname = gv_so_it "Sales Order No+Item number
fobject = gc_obj
save_direct = 'X'
fformat = '*'
TABLES
flines = it_temp "Data to populate text tab with
EXCEPTIONS
no_init = 1
no_save = 2
OTHERS = 3.
CLEAR it_date.
ENDLOOP. "it_date
and call that Z function module in update task in userexit_save_document ,there vbak-vbeln or xvbak-vbeln will have the SO number .
Please reward if useful.

Sales Order Creation with reference to Contract

Hi all ,
Existing Setup in the System:
1) I have a contract created with a validity period of 30 days. When i create sales order with reference to contract, then i get a pop-up box, from the box i can select my contract.
2) I have a Lead time configured as 5 days for the Sales document type , I,e when I create sales order I can see my Requested delivery date is always system date + 5 days.
3) I have a Pricing date configured as Todays date. Therefore when I create sales order I can see pricing date becomes the system date.
Execution of Sales Order:
4) When I create Sales Order with reference to contract document. Always Requested Delivery date is compared with Contract Validity Dates.
Example: Contract Validity 01/03/2008 - 31/03/2008
Sales Order: Sales Order Creation date -> 19/03/2008, Pricing Date: 19/03/2008 Requested delivery date 24/03/2008.
REQUIREMENT IS:
But my requirement is when i create Sales Order it should consider System date or Pricing Date( since pricing date is today date) for to compare with contract validity dates.
Can it be done with standard config or do we need to some type of custom? Appreciate your help
Thanks

Hi ,
As said when I create Sales Order with reference to contract document. Always Requested Delivery date on Sales Order is checked against Contract Validity Dates.
But i want Pricing date in Sales Order should be checked against Contract Validity Dates.
Can someone suggest me on this?

Performance of Sales order creation on Business Suite on HANA

Hi,
I understand that HANA column tables are read and insert optimized. I would like get some clarification on the following scenario.
Assume that in the ECC (non HANA DB) the sales order creation process is taking few hours to complete due to the sheer number of line items and associated bill of materials, serial numbers etc. If the same process is running on the Business suite on HANA system will there be any considerable performance improvement (because HANA column tables are insert optimized)?
Thanks for your help on this.
Thanks
Vinod

Yes Vinod,
that is the general idea.
For more details please have a look at Hasso Plattner's latest book A Course in In-Memory Data Management: The Inner Mechanics of In-Memory Databases.
R/3 updates the row table based on V1 or V2 priorities and writes the changes to the change log tables in the background.
With HANA application we can eliminate the need for the change log tables and table locking, by inserting the changes for particular fields into the columnar tables of the application with a time stamp immediately, and therefore also enabling real-time reporting.
For traditional RDBMS based applications the notion was that the faster read from the row tables which only hold the latest updates justifies the update of the changelog tables. In order to optimize this update process required by the traditional RDBMS-based systems, a single sales document was split into many smaller tables, like for example header table VBAK and item table VBAP and separate status tables for these header and items, which also made it more challenging to build reports on the complex set of individual tables.
Indices and aggregates could be more easily build from the single row records, but on the flipside after each update to the row table, the indices and aggregates needed to be re-build or scheduled for rebuild at a later point in time. Not only the application-build index tables and aggregates, but also the secondary index tables created by the DBA tuning efforts.
Overall tons of overhead especially for business processes with a many updates like sales order re-scheduling based on MRP runs.
With HANA this is no longer necessary as the latest information and the time travel from the columnar store can be accessed instantaneously across all inserts and therefore eliminates the need for any overhead of the index and aggregates as well as the changelog tables. In addition the split of document information into many smaller tables can now be avoided, so that we might not see any header tables and their dependent tables anymore.
We will provide more updates as they become available in the S/4 SAP S/4 Business Suite on SAP HANA (FAQ)
Thank you
erich

LSMW Sales Order creation using Bapi method

Hi folks ,
iam doing Lsmw bapimethod ,sales order creation .In the step start idoc processing iam getting error "Has Not been Accepted for Processing ",why iam not getting plz let me know points will be awarded for all answers .

Hi,
You need to set the IDOC settings in the initial LSMW screen. It will be there in menu path.
Award points if helpful
Regards,
RamaKrishna C

Block sales order creation based on material qty

Hi,
In my scenario i want to block the sales order creation based on material qty , how i can do this?
Example:
Material qty below 100 = able to create sales order
Material qty above 100 = not able to create SO
Thanks,
Arun

Hi
For restricting the order if it is less than a specified qty, you can maintain the 'min order qty' in material master.
But your requirement is the other way round - Restrict order if it is more than specified qty.
In this case, you need to use the following sales order exit in progran MV45AFZZ
u2022 USEREXIT_SAVE_DOCUMENT_PREPARE
Use this user exit to make certain changes or checks immediately before saving a document. It is the last possibility for changing or checking a document before posting.
The user exit is carried out at the beginning of the FORM routine BELEG_SICHERN.
Hope this helps.
Regards
Madhu

Need help in sales order creation

Similar Messages

Maybe you are looking for