why you do not require document flow when your are copying of other document?? its standard behavior, always better not to change any standard behavior.
Because sometimes the user copy a sales order to have got yet data into new sales order, but there isn't a process flow between two document.
I have seen in the customizing that in Copying Control: Sales Document to Sales Document there is at item level the field "Update document flow", i can use it for my scope, setting it to value = blank
When you don't want to have a relationship between to doc and want use only for reference then you can use - Dynamic Product Proposal or simply, user can refer the items from existing doc (to do this in sales order overview screen, press CRTL+F11, explore the option-easy without config )
A product proposal is a list of products for a specific customer that is automatically proposed during sales document processing. You can decide for yourself which materials should be displayed as product proposals in the sales document. You can also determine the sequence in which the materials appear in the product proposal.
During sales document processing, the system displays a product proposal in the item overview according to the customer and the business transaction. It displays the material number, material description, and historical order quantites in the sales unit last used. To use a material again, you just have to copy it. The system does not run the standard checks (pricing, availability, incompletion, material determination, free goods determination and so on) until you have entered the order quantities.
The product proposal is both an entry help and an aid to sales support and promotions. It is particularly useful in Telesales, where the employee automatically receives a display of all the materials that are of interest to a particular customer. This helps them to provide appropriate advice to the customer quickly and easily. The sales document history enables you to analyse the purchasing behaviour of a customer and recognize early on if it changes, for instance, when the customer suddenly stops ordering a product.
The product proposal differs to cross-selling in that it is dependent on the customer and sales area, and is displayed in the sales document as soon as you have entered a customer. Cross-selling, on the other hand, is triggered by a material. In other words, the system proposes cross-selling materials according to the material or a characteristic of the material you have entered.
You can determine the product proposal from different data sources:
-Order history
-Listed materials
-Excluded materials
-Item proposal
-Customer-material info records
-Customer-specific data sources
You can combine materials from these data sources to create a product proposal. The system then accesses the data sources either online or in the background.
To define a product proposal for sales document processing, you must carry out the following activities in Customizing:
-Define customer procedure for product proposal
-Define document procedure for product proposal
-Assign document procedure for product proposal to order types
-Maintain table of origin for product proposal
-Define product proposal procedure and determine access sequences
-Maintain procedure determination (in background) for product proposal
-Maintain procedure determination (online) for product proposal
The product proposal procedure determines how the system displays the product proposal in the sales document. For instance, if the system has accessed the order history, it determines how many columns should be displayed in the sales document, in which period intervals thehistoric order quantities should be displayed (for instance, day, week, or month), and most importantly, the sequence in which the system should access the data sources (for example, order history, listing, exclusion).
The product proposal procedure depends on the:
- Customer determination procedure
The customer procedure determines which product proposal procedure the system automatically uses when you create a sales document for a particular customer. It is specified in the customer master record per sales area.
- Document determination procedure
The document procedure determines which product proposal procedure the system automatically uses for a certain document type. The document procedure is stored as a key in the header for the sales document type.
If you use online processing, the product proposal procedure is determined according to the customer and document determination procedures.
If you use background processing, the product proposal procedure is determined according to the sales area in the customer master and the customer determination procedure. It does not use the document determination procedure because the document type is not recognized in background processing
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.