New Sales Process

Dear Experts,
In my company we want to a implement a new distribution process. As per process we have abolished all C&F and make them super distributors. We will sale to them. Till this process is very clear. Now what company want is Super distributors Sales data, Inventory Data and Collection data from their stockiest. All super distributors are ready to user SAP.
Is there any standard solution available in SAP like Web portal or any third party solution from which we can upload data directly in SAP.
Regards,

Hi Dear,
You have to do this with Variant configuration.
configuration of mto
You can check and search the forum for MTO and Variant config there are lots of Doc.
Thanks,
Raja

Similar Messages

Customer Service - Extended Warranty Sales Process

Hi All,
I want to implement Extended warranty sales process in sap. Here, dealer will send extended warranty form to company. Company wants to capture warranty related information (such as Vehicle number, Chassis Number, Date) in sap and want to sell warranty to dealer.
Monthly once company will give discount to dealer based on performance. How to give discount to dealer monthly?
I want to know the following details:
Material type
Item category
Process flow
How to capture warranty information?
Thanks in advance,
Babu

Thanks for your reply......
I have created new sales document type for extended warranty sales. I am using variant material for capturing dealer's requirement in va01 itself.
Now my client dont want to create invoice for that sales order.
With this Extended warranty sales order reference, they will create manual posting in Finance.
Actually, they don't want to treat this as a revenue. This is a liability when they sell extended warranty to customer and after the extended warranty period is over (after 3 years), if the vehicle doesnt come for ext warranty claim then it will be treated as income.
Is it correct process to leave extended warranty order (sales order-va01) without doing billing ?How can i proceed further?
Thanks in advance,
Babu

Creation of new Sales order

Hi,
       While creating a new Sales Order(tcode VA01) depending on the material, Item category will be generated and depending on the Item category purchase requisition screen(ME51n) will be automatically opened and PR will be created.
Now to automate this process, BAPI_SALESORDER_CREATEFROMDAT1 will be called to create the sales order. But the requirement is that we need to pass Requisitioner and Vendor to the BAPI for creation of PR.
But in this BAPI there is no option/field to pass Requisitioner and Vendor. So is there any other BAPI/Function Module where a new Sales order is created and also we can pass Requisitioner and Vendor required for creation of new PR.

REPORT ZSALESORDER.
Parameters
Sales document type
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 .
SELECTION-SCREEN END OF LINE.
Complete Deliver
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text10 FOR FIELD p_autlf.
PARAMETERS: p_autlf TYPE autlf DEFAULT 'X'.
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.
DATA: lt_schedules_ink    TYPE STANDARD TABLE OF bapisdhead1
                         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'.
v_text10 = 'Complete delivery'.
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'.
*Complete delivery
    header-COMPL_DLV = p_autlf.
    header-COMPL_DLV = 'X'.
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'.
item category
itemx-ITEM_CATEG = 'X'.
APPEND item.
APPEND itemx.
ITEM DATA
itemx-updateflag = 'I'.
Line item number.
item-itm_number = '000020'.
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.
Fill schedule lines
lt_schedules_in-itm_number = '000020'.
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 = '000020'.
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.

Regd creation of New Sales Order Type - Credit Memo Request

Hello Gurus,
I have created a New Sales Order Type as per the given requirements. This is a Credit Memo Request. I have done all that are needed from SD perspective.
Can you please let me know what needs to be done from FI-CO perspective when a New Sales Order Type is created and this is a Credit Memo Request. If some one can let me know the customizations that needs to be done it will be very helpful for me.
Thanks,
SNK.

Hi,
As per my understanding, there is nothing to be required from FI-CO perspective, in case when you defined a document type in SD.
During the sales order processing the SD-FI interface happenes for following activities
1) Credit check (In case you use Credt management)
2) Tax determination
For more knowledge
go through the link given below.
http://www.sap-img.com/sap-sd/link-between-sap-sd-mm-and-fi.htm
Hope it helps,
Regards,
MT

What's new in Process Control 2.5?

Hi,
I'm looking for information about what is new in Process Control 2.5(compare to the 2.0 version)
Thank you in advance for your help,
Regards,
Julien

The key innovation of PC 2.5 is the user experience. The highlights of this innovation are:
A new user experience based on work centers which mimics the way compliance and business users actually work
A combination of top session management and sidebar navigation leads to cleaner, more intuitive design
Broad availability of relevant contextual information as appropriate, in the form of documents and links
Pervasive search functionality, with list filtering and sorting capability to deliver information as the user needs it
Automated testing
Delivered scripts cover Financials, Procure to Pay, Sales and Distribution, and more...
Rule parameters passed to scripts extract data from the source ERP system and return evaluation results with related issues or exceptions to Process Control
Query-based scripts use SAP Query to provide additional flexibility
Use of standard SAP and customer-created reports can be returned as part of evaluation and marked as requiring review to determine whether the evaluation passed or failed
ANd much much more

Down payment process for Poland, new business process or not ?

Hello,
I'm a little bit confused about implementation down payment process for Poland.
The OSS-notes 818079 and 1007635 describe a solution for this.
How do I have to implement the correct down payment process for Poland ? Do I have to create an extra business process with new sales order type, new billing type, separate calculation procedure, new output type and so on ?
Or is it possible to use existing business processes in sales and distribution for down payment processes ?
Thanks in advance
Holger

hi,
Check the process for down payment processing
The following Customizing settings have to be made for down payment processing:
Settings for the billing plan - To activate the billing plan function, maintain the materials, for which you wish to process down payments, with item category group 0005 (milestone billing). This gives the item type TAO via item type determination. The item type TAO calls up the billing plan function.
You need to implement the following activities in the billing plan for down payments:
Maintain deadline category - This determines the billing rule (percentage or value down payment) for the down payment request. The system assigns billing type FAZ (payment request) defined in the standard system with billing category P. (For the billing type FAZ there is the cancellation billing document type FAS in the standard system).
Maintain the deadline proposal - Use the down payments that are due for the proposed deadlines.
Maintaining a Pricing Procedure with the Condition Type AZWR:
In the standard system the condition type AZWR is delivered for the down payment value already provided but which has not yet been calculated. You must include this condition type in the relevant pricing procedure before output tax.
Enter condition 2 (item with pricing) and the calculation formula 48 (down payment clearing value must not be bigger than the item value) for the condition type AZWR.
Before the condition AZWR you can create a subtotal with the base value calculation formula 2 (net value). If the condition AZWR is changed manually, you can get information on the original system proposal from the subtotal.
Maintain the printing indicator - The pricing procedure can not be marked as a transaction-specific pricing procedure (field Spec.proc.) The condition type AZWR has the calculation type B (fixed amount) and the condition category E (down payment request / clearing).
Maintaining the Billing Document - In the standard system there is the billing type FAZ (down payment request) and the billing type FAS for canceling . The down payment is controlled using the billing category P of the billing type. A billing type becomes a down payment request when the billing category P is assigned. You have to maintain blocking reason 02 (complete confirmation missing) for the billing documents and assign it to billing type FAZ.
Copying control - Copying requirement 20 must be entered in copying control at item level for the down payment request. In the standard system the order type TA for copying control is set up according to the billing type FAZ for the item category TAO.
Copying requirement 23 must be entered in copying control at item level for down payment clearing. In the standard system the order type TA for copying control is set up according to the billing type F2 for the item category TAO.
Financial Accounting settings - A prerequisite for down payment processing is that the account is assigned to the underlying sales document. To do this, change the field status settings in Customizing as follows:
Set reconciliation accounts (transaction OBXR) - For the `received down payments' and `down payment requests' from
the G/L accounts you have selected, you should assign the field status definition G031.
Maintain accounting configuration (transaction OBXB) - For the down payments (posting key ANZ in the standard system) and the output tax clearing (posting key MVA in the standard system), you must maintain the posting key.
You must also carry out a G/L account number assignment for the tax account.
Maintain the posting key (transaction OB41) - For posting key 19, set the sales order as an optional field !!!
Maintain the field status definition (transaction OB14) - For field status variant 0001, field status group G031, set the
sales order as an optional field !!!
Assign the company code to the field status variants (transaction OBC5)
chandu

Sales Processing

Hi Everyone,
I'm trying to figure out what the correct process would be for the following situations:
1. A sales order is created and copied to a delivery at the time of shipment. The shipment is incorrectly processed with everything shipping (the shipping department forgot to backorder an item). They do a return on the delivery for the item overshipped. However, at this point the sales order is closed because it was accidentally shipped in full and the return of the item does not open it back up.
When the company would like to ship the remaining quantity, how should they do it properly? It appears they would have to create a new sales order for only the quantity that was backordered and will be shipping, but how will this affect sales history? And is there a way to link the second sales order to the first so when a report is run or the customer goes back to the order they see it relates to the other order? Or is a comment in the remarks field to this effect the best way to "link" this.
2. And what would be the best process if an A/R invoice is created with let's say an incorrect price? I understand you would create a credit memo. But is there a way to do a simple price adjustment on the credit memo screen? Or must you credit the line in full? And once the line is credited in full, the AR invoice does not open back up so the line price can be changed. Would you just add a new A/R Invoice then at the corrected price? Is there anyway to link the new corrected A/R invoice to the delivery and the sales order manually, so the user can backtrack through the documents in the future? Or would you only be able to add a comment?
I appreciate everybody's help trying to work through the workflow of the system.
Thank you,
Amanda

Hi Amanda--
There are probably multiple ways to do this, but here are my suggestions:
1. You will need to create a new sales order in to ship the item that should have been backordered. Use the same customer reference number as the original SO, and enter something in the Remarks field to tie it to the original document number.
The effect on sales history depends on how you look at sales history. If you just look at orders, it will appear that the item was sold twice. But if you look at invoices, it will be correct, because the when you did the return, you closed that line on the delivery, and it won't appear on the invoice for the first shipment; there will be a separate invoice later.
2. There are two ways to handle the incorrect price on an invoice. As you know, you cannot change an invoice once it is entered. You can enter a service-type credit memo for the amount to be credited - that is the quickest and easiest way to handle it, but you are left with an incorrect gross profit on the original invoice. The best thing to do is to create a credit memo that is copied from the incorrect line on the invoice, so that it is credited completely (the item will be returned to stock). Then issue a new invoice for the item at the correct price. This removes the item from stock again, and records the correct gross margin for the sale. Again, use the customer reference number and remarks to relate the new invoice to the original one.

A query to get all sales processed in 2007 ?

Hi All,
I got a requirement from user saying
" We have situations where "new" sales get processed against already existing or "old" sales orders. I need a query which shows all sales processed in year 2007 by sales order or whatever other identifier that is used"
This is not making any sense to me. Can anyone help me with this ? Is there something to do with ship date or anything? Please let me know!!
Thanks in advance
Prathibha

Hi Prathibha,
The only idea that came to my mind is the following: your customer sends order in a regular interval (weekly, monthly…) under a number that represents an agreement between you and your customer.
Under this scenario, you have one order created in the previous period from customer A that was partially shipped. In the current period, customer A sends a new order to you, but the quantity sent by your customer includes the balance. So, if new_quantity greater than old order balance, you will need to add an order with the balance.
Still under this scenario, the report could all orders in OM posted/shipped in 2007 under this agreement.
Just an idea, hope it helps,
Ketter Ohnes

Sales Process for Packaging material (VERP)

Hi All,
I have a business requirement to set up the sales process for Packaging materials and the material type is VERP.
But system will not allow me to create Sales order using the same material because material category VERP needs to be added for the Order type OR.
VERP materials not authorized to create sales orders. I think we need toset up new process.
Pls help me if you have any idea about to set up the nbew process.
Kindly help me..
Regards,
SK

as mentioned earlier,
1. See to it that the material with Material type VERP has tabs Sales org 1, Sales org 2, Sales:General/ Plant.
This can be configured in OMS2. Maybe already there in standard configuration
2. In VOV4, assign the item category to your Sales doc type and It cat. gr. VERP
Then in VA01, test by creating a sales order.

How to integrate a sales process across multiple ERP systems with SOA?

Over time we have merged with multiple companies that used to run on their own ERP system. In the past we concerted them to our own R/3 instance. Having recently upgraded from R/3 4.6 to ERP 6.0, we want to transition to a SOA architecture for integrating stand-alone ERP systems. We are looking for best practices on how to start this transition; i.e., how to use SOA to implement an Order-to-Cash process across separate ERP systems.
Here is our scenario:
The same products are sold through ERP system A and ERP system B. However, each system represents a different company code with its separate manufacturing plants. Both systems evolved independently and presently have separate master data. How do you enable a sales process that dynamically (depending on inventory availability) gets the product either from a plant on system A or B? How do you implement a triangular sale that covers both ERP systems?
I am looking forward to learn from your experiences and your advice.

Hi Bernard,
Like most SOA scenarios, first your scenario requires a detailed fit gap analysis to see which of your existing ERP systems best meet which business process that you want to accomplish at an organisation level. It is only after that, that you can decide which capabilities of SAP SOA can you leverage and how.
Broadly speaking, SAP's SOA paradigm provides several approaches which you could use depending on your scenarios. For example, if you only need a brokerage between two or more systems (updating or retrieval of data) either synchronously or asynchronously, your best bet is PI (preferably 7.1 because of its ESR and Services Registry). On the other hand, if you require a new application that acts as a controller of flow or processing across various systems, you could use the Composition Environment which provides you with a toolset to build composite applications across various systems (for instance, by registering services from multiple systems on the Services Registry, and then consuming it from say a WebDynpro application).
The following document might provide you with more insight on this:
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/809db91f-9bdf-2910-93be-ca4f0853f929
Hope this helps!
Regards,
Romit

Sales Process And EDI Idocs Integration

Hi Friends,,
Good Day To You All !!!!
Please enhance my knowledge with your valuable reply.
I am new to ABAP and would like to learn the following .
1. Sales process - Starting from the Purchase Order Till shipment is created (All TCodes and the definations of the terms used like procurement , scheduled line,handling unit and all those terms coming into picture till the Sales process comes to an end).
2 . Idocs - Transaction Codes,Definations Of Terms like message types , basic types etc, etc,
I need the above information to get a clear picture of the process taking below.
What if an interface exists between SAP and a Non-SAP system(say Siebel system ) .The customer being the Non-SAP system and the Vendor our SAP system . Then the flow of the sales process taking place , with the PO coming from the Non-SAP system through inbound idoc and immediate ATP date going from SAP through the outbound Idoc..the process continues with the creation of delivery then shipment.Each of these triggering their respective idocs .
And the idocs update the corresponding status in Siebel .
I hope you guys would have understood by now , as to why i need the information on Sales Process and Idocs.
Thanks.
With regards,
Learner .
Edited by: SAP Technical Consultant on Oct 16, 2008 9:08 AM

Hello,
         If you want to Set up an Inbound Process for Sales Order Changes, all you have to do is
1. Maintain the Partner Profiles for the Inbound Message Type & Process Code in WE20.
2. The Assignment for Function Module IDOC_INPUT_ORDCHG is already available in WE42 Transaction for the Process Code ORDC. So, you don't have to worry about setting up the Process Code.
3. Take a Sample IDoc of Type ORDCHG Message Type in WE19 and try posting it for the Given Sales Order. If you would like to know more about what it does, Post it using Debugging Mode.
            The above Process is for Sales Order Changes via Inbound IDoc. Below are the Steps for the Outbound Delivery IDoc Trigger.
1. The Process Code DELV already has the Selection Program IDOC_OUTPUT_DELVRY in Transaction WE41. So, you dont have to worry about Setting Up the Process Code.
2. Also, check your field list. Open the IDoc Type DELVRY05 in the Transaction WE60 which is for IDoc Documentation. Check if all the Fields mentioned in your the list that you want to send are available in the Standard IDoc Type. If not, create a Custom Segment in WE31 & Assign the Custom Segment at an appropriate place in the Extended IDoc Type in WE30.
     All the Standard Segments / Fields available in the DELVRY05 IDoc Type will be automatically be populated by the Standard Selection Program IDOC_OUTPUT_DELVRY. However, if you have an IDoc Extension and would like to populate the Custom Segment / Fields, then you'll have to use the Customer Exit EXIT_SAPLV56K_002 in which you can write Code for populating the Custom Segments / Fields.
3. The Most important Thing that we need to take care of is Message Control Configuration while handling the Outbound EDI Scenario.
4. You need to Set up the Output Type for the Delivery Application (V2) for which you need to maintain Condition Records so that the Output Type is proposed automatically when the Delivery is being Saved.
5. In general, the Message Control Configuration is done by the Functional Team. So, ask your Functional Consultant to set up the Message Control Configuration for the Delivery IDoc Trigger.
Hope it was clear enough.
Thanks and Regards,
Venkat Phani Prasad Konduri

Integrated Sales Process between two related companies

HI Friends,
Would appreciate if any of you can share their experience on the above subject.
What is proposed is that Company A and Company B (both under the same management and related) shall have an integrated sales process, whereby Company A will directly enter the stock transfer orders in Co. B and the goods will be directly shipped to customers of A by B, bypassing the need of GRN and MIRO in Co. A as no POs will be issued by A to B.
However Co. A shall issue the Sales Invoices to its customers to whom the goods have been directly shipped by B and would record the liability yo Co. B thru FI Invoice. This is a new concept we are coming across and would like the members to share their experience with regard to analysis and VAT reporting challenges faced by finance in terms of internal controls and compliance.
Thanks !
RN

Hello RN,
Check with intercompany sales scenario;s in SD module. Company B receives the PO from end customer > In company B books created as Sales order with ship to party and bill to party as end customer & but delivery plant should be Companies A plant where goods shipped or manufactured.
Based on above SO company A will produce the material > shipped to end customer in lieu of company B. The follwoing entries post in company A >
Goods shipped / PGI :- COGS Account.........Dr
                                      To FG Account................Cr
Billing to Company B with agreed price between A & B :-
                                  Company B ..............Dr
                                     To Intercompany Sales account........Cr
Company B books entries :-
While intercompany billing :- ( It's through EDI) ( It is nothing but MIRO)
                                 COGS account...............Dr
                                    To Company A account............Cr
Billing to End customer :-
                                Customer account..........Dr
                                    To Sales account................Cr
Regards
Mani Kumar

Automatic Batch Determination is not happening for New Sales Order Type

Dear Experts,
I have created a new sales order type ZBPY - For Free Sales, but automatic batch detrmination and batch pick up is not happening for new sales order type, but it is activated for all the other sales order types in Production Server, can any body let me know the steps how to map this new order type to batch management and let it behave like other order types.
Thanks in Advance.
Saravanan(EKS).

Hi Saravanan,
Kindly check the following steps for automatic batch determination.
1. First check the material is maintained with batch in the warehouse management.
2. Maintain new entry for search procedure for batch determination with the new created doc type.
3. Maintain new entry for automatic batch determination for sales order or automatic batch determination for delivery ( This depends on the business process of our client, whether they want to determine the batch with sales order or at the delivery level. check this and make new entry)
4. Create Batch using T.code MSC1N with proper date of manuf. and SLED.
5. Create Batch Search Strategy using T.code VCH1 with proper strategy type.
6. Maintain stock with active batch. check this with t.code LS26 or LS24.
regards
Ravishankar M

For new Plant should we have to create a new sales organization?

Hi Experts,
I am going for one roll out project. In that we have to create new plant, so should i have to create new sales organization or else we can use the same. And also tell me what are the benefits & disadvantages of that.
Thanks & Regards
Chavi Patle
Edited by: chavipatlesd on Jan 30, 2011 8:33 AM

hi
i will say only one logic here.
if you define the plant or new plant you need to extend all the other organisational units for it right.
then i there is no need for creation of new SALES ORGANISATION on the same.
please take the advice of your PM in this regard he might be having different views from reporting perspective and might be your roll out project needs a new sales orgn or not.
if you ask us thre is no need for creating a new sales organisation on the same.
advantages:
if there is a really need for creating a new sales orgn as wellas plant this mihgt be for reporting perspective only & analysis will be very clear.
disadvantages:
this is not a disadvantage but from Enterprise Structure point of view master data will increase ofcourse this master data is needed for smooth processing of SYSTEM
hope this clears your issue.
balajia

What is the impact on MM if assign new sales org to sales order type?

hi expert!
need to ask you guys, what is the setting need to be done if on sales side they want to assign a new sales org,distribution channel and division to sales order type for drop shipment process? Do we only need to make sure that purchase org has been assigned to company code of the sales area?
Thanks.

Sales Organisation has to be assigned to a company code & Sales view of the material has to extended to this new sales organisation using T code MM01.
Regards
Bhavesh Mistry

New Sales Process

Similar Messages

Maybe you are looking for