APO - Sales order creation need help

Hi Guys ,
I am new to SAP APO . We are trying to create 13000 sales order everyday using abap BAPI - BAPI_SLSRVAPS_SAVEMULTI2.
it is taking more than 2 hours . Can you guys help me is there any other way to create Sales order .
I need to know transaction code to create Sales Order foreground .
Please help me .
Thanks a lot.
Regards
Prabhu

can you help me with the fields of the bapi (BAPI_SLSRVAPS_SAVEMULTI2) that i must fill in order to create a Sales order correctly?
Im trying to CIF sales orders changing the location(origin) with a Transportation Zone using the enhancement CIFSLS03 (ECC) but i think there is some limitation to create this orders in location type 1005.
thats why im trying to prove first with the bapi if it will be possible to create orders independent from CIF limitations.
Can anyone help me?

Similar Messages

User exit to control the sales order creation

Hi All,
I have a business scenario, where a specific account group customers Business doesn't want to sell the goods .SAP should not allow you to create a sales order.
Which user exit will solve my requirement?
could you please help me..
Regards,
SK

Hi Prakash,
Thanks for the reply. Actually these customers are created as a Agents and we are using these customers in Commission rebates. So at the time of Rebate partial credit memo, then these agents should be active otherwise system will give the error.
So what i am thinking is, Standard sales order creation needs to be restricted so that users can not able to create standard order.
So can you suggest is there any user exit can be used to prevent creation of standard order for these account group and order type xxx?
Regards,
SK

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 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

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

Sales Order creation in R3 system using APO TLB functionality

Dear All,
Is there a way to create / trigger sales order creation in the R3 system using TLB shipments or using TLB functionality ?
Kindly describe the steps
Thanks
Sridhar R

Hi,
During the AC for the sales Order, the delivery date for the sales orders depends upon whether you are checking with Replinishment lead time or not.( Defined for the combination of checking group and Checking rule in Checking Scope)
The RLT is the time necessary to provide a material either by in-house production or by external procurement.
For external procurement, the replenishment lead time consists of the purchasing department processing time, planned delivery time, and goods receipt processing time and the ATP check only includes the planned delivery time.
1.If the replenishment lead time is taken into consideration,the availability is checked only for requirements within the replenishment lead time. Requirements outside the replenishment lead time are considered to be available as the system assumes that these materials can be provided by planning within the replenishment lead time.
2. If a requirement cannot be covered by receipts, the end of the replenishment lead time is the earliest date that the material can be confirmed.
3.If the replenishment lead time is not taken into consideration, the availability is checked for each requirement time without taking the replenishment lead time into consideration.
Thanks,
nandha

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

Reg:IDOC -sales order creation

Hi All,
I am trying to create sales order through IDOCS.Basic type is SALESORDER_CREATEFROMDAT201.
My requirement is to know any user-exits where in I need to add to my code to hardstop sales order creation if the storage location which I am passing is marked for deletion.
Kindly reply as soon as possible.
Regards,
Kaveri

Hi,
Check this one it will help u how to enhance the idocs.
If we wnat to extend the idoc use the segments for adding the fields. use the tcode WE30 and we31.
Please reward points if it is useful.
Go through the following Steps For ALE/IDOC
ALE IDOC
Sending System(Outbound ALE Process)
Tcode SALE ? for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ? Create Model View
Tcode BD82 ? Generate partner Profiles & Create Ports
Tcode BD64 ? Distribute the Model view
Message Type MATMAS
Tcode BD10 ? Send Material Data
Tcode WE05 ? Idoc List for watching any Errors
Receiving System(Inbound ALE )
Tcode SALE ? for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ? Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 ? Idoc List for inbound status codes
ALE IDOC Steps
Sending System(Outbound ALE Process)
Tcode SALE ?3 for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 !V Create Model View
Tcode BD82 !V Generate partner Profiles & Create Ports
Tcode BD64 !V Distribute the Model view
This is Receiving system Settings
Receiving System(Inbound ALE )
Tcode SALE ?3 for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 !V Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 !V Idoc List for inbound status codes
Message Type MATMAS
Tcode BD10 !V Send Material Data
Tcode WE05 !V Idoc List for watching any Errors
1)a Goto Tcode SALE
Click on Sending & Receiving Systems-->Select Logical Systems
Here Define Logical Systems---> Click on Execute Button
go for new entries
1) System Name : ERP000
Description : Sending System
2) System Name : ERP800
Description : Receiving System
press Enter & Save
it will ask Request
if you want new request create new Request orpress continue for transfering the objects
B) goto Tcode SALE
Select Assign Client to Logical Systems-->Execute
000--> Double click on this
Give the following Information
Client : ERP 000
City :
Logical System
Currency
Client role
Save this Data
Step 2) For RFC Creation
Goto Tcode SM59-->Select R/3 Connects
Click on Create Button
RFC Destination Name should be same as partner's logical system name and case sensitive to create the ports automatically while generating the partner profiles
give the information for required fields
RFC Destination : ERP800
Connection type: 3
Description
Target Host : ERP000
System No:000
lan : EN
Client : 800
User : Login User Name
Password:
save this & Test it & RemortLogin
3)
Goto Tcode BD64 -- click on Change mode button
click on create moduleview
short text : xxxxxxxxxxxxxx
Technical Neme : MODEL_ALV
save this & Press ok
select your just created modelview Name :'MODEL_ALV'.
goto add message type
Model Name : MODEL_ALV
sender : ERP000
Receiver : ERP800
Message type :MATMAS
save & Press Enter
4) Goto Tcode BD82
Give Model View : MODEL_ALV
Partner system : ERP800
execute this by press F8 Button
it will gives you sending system port No :A000000015(Like)
5) Goto Tcode BD64
seelct the modelview
goto >edit>modelview-->distribute
press ok & Press enter
6)goto Tcode : BD10 for Material sending
Material : mat_001
Message Type : MATMAS
Logical System : ERP800
and Execute
7)goto Tcode : BD11 for Material Receiving
Material : mat_001
Message Type : MATMAS
and Execute --> 1 request idoc created for message type Matmas
press enter
Here Master Idoc set for Messge type MATMAS-->press Enter
1 Communication Idoc generated for Message Type
this is your IDOC
Change Pointers
I know how to change the description of a material using ALE Change Pointers.
I will give the following few steps
1) Tcode BD61---> check the change pointers activated check box
save and goback.
2) Tcode BD50---> check the MATMAS check box save and comeback.
3) Tcode BD51---> goto IDOC_INPUT_MATMAS01 select the checkbox save and comeback.
4) Tcode BD52---> give message type : matmas press ok button.
select all what ever you want and delete remaining fields.
save & come back.
5) 5) go to Tcode MM02 select one material and try to change the description and save it
it will effects the target systems material desciption will also changes
6) goto Tcode SE38 give program Name is : RBDMIDOC and Execute
give Message type : MATMAS and Executte
ALE/IDOC Status Codes/Messages
01 Error --> Idoc Added
30 Error --> Idoc ready for dispatch(ALE Service)
then goto SE38 --> Execute the Program RBDMIDOC
29 Error --> ALE Service Layer
then goto SE38 --> Execute the Program RSEOUT00
03 Error --> Data Passed to Port ok
then goto SE38 --> Execute the Program RBDMOIND
12 Error --> Dispatch ok
Inbound Status Codes
50 Error --> It will go for ALE Service Layer
56 Error --> Idoc with Errors added
51 Error --> Application Document not posted
65 Error --> Error in ALE Service Layer
for 51 or 56 Errors do the following steps
goto WE19 > give the IDOC Number and Execute>
Press on Inbound function Module
for 65 Error --> goto SE38 --> Execute the Program RBDAPP01 then your getting 51 Error
regards,
satish.

Userexit/Badi for vendor or enduser addition/change in sales order creation

Hello Gurus,
I need a userexit/badi that gets triggered on the addition/change of partners in sales orders
I need to make some validations when the user adds/changes the vendor or
enduser in the sales order creation.
I tried many exits that I could find from forum but they were not able to asist.
Any help would be much appreciated.
Thanks in Advance,
Sumit.

Well, if all else fails, USEREXIT_MOVE_FIELD_TO_VBAK will definitely be called when you change partners... but of course it will be called much more often than at only partner changes. Still, internal table XVBPA shows the current partners, so you could compare its content with the earlier state of the table to recognize a partner change you're interested in.
Strangely, the usual Y-table (YVBPA) is not populated, not sure why, otherwise the comparison would be even easier.

Sales order creation -pricing- IDOC processing

Hi All,
Issue is related to pricing procedure and condition types while processing the IDOC for sales order creation.
The condition type ZSTD maintained in the pricing procedure AAAA, has reference condition type as ZZZZ, when we are processing IDOC, system is throwing error as " condition type ZZZZ, is not maintained for A V AAAA.
This error will not populate when we create the sales order manually.
Kindly let me know if programs needs to be checked and or any configuration mistakes involved in this.
Regards,
SAN

>
Vivek Baddula wrote:
> Hey Teju,
>
> Could you pls put me the block of code how you are populating to the idoc edidd. So that we can guide you.
>
> And also tell me the message status 51 in IDoc what it is showing , and also see the segment( maybe E2EDP05) specific to pricing for the IDoc you populated.
>
> Regards,
>
> Vvieks
>
> 'Grow and help others to Grow'
Vivek,
Thanks for the reply.
Status 51 reads "condition ZPRL is missing in pricing procedure A V ZPRINT, WE are not passing any value as a part of tsting. The system should pick price values from condtion record.

Sales order Creation date

Hi All,
I see that the sales order creation date in VBAK is suppose 2009.06.16 and in VA03 if i see th document flow the date is 2009.06.15. and quatation date is also 2009.06.15.
Which date is the correct Sales order date.If va03 one is correct what is the source table of this date?
PLease commnet .
Thanks in advance,
Swati

Hi ,
Let me know in which field you are looking into in VBAK table
Please let me know if you still need any help.
Thanks and regards,
Rajeshwar.

APO - Sales order creation need help

Similar Messages

Maybe you are looking for