After creating a sales document type in tvak
after creating a new sales document type in tvak what next to link it to BP number.
Hi
it should be done via configuration, not using the tcode
goto SPRO
press F5
search for SALES DOCUMENT TYPES
<b>in sales & distribution
sales
sales documents
sales document header
define sales document types</b>
there you have to add extra new entries
Regards
Anji
Similar Messages
-
Why should we create a new sales document type
I want to know the actual reason behind creating new sales document type when the standard document is available
General procedure when setting up sales document types
You have three options for configuring new sales document types:
1. Change an existing sales document type.
2. Copy an existing sales document type and change it according to your requirements.
3. Create a new sales document type.
Recommendation
For small changes, SAP recommends that you copy similar existing sales document types in the standard SAP R/3 System and make the appropriate changes. Small changes might, for example, be, a changed description, a different number range or a different increment for the numbering of items. The name is to start with the letter Z as SAP keeps this range free in the standard system.
This procedure has the following advantages:
All the specifications of the existing sales document type are copied. In particular, the data concerning, for example, partner determination, pricing or document flow which you would otherwise have to edit manually is copied.
You can test your new sales document types in respect to the settings made without having to edit the other settings.
When copying sales document types, item categories and schedule line categories, the SAP R/3 System automatically creates a log with the copied data. Using the log, you can check whether all of the copied data applies to your sales document type or whether you need to make changes.
Actions
1. If you need to make further changes, you should define new sales document types. To do this, you enter an alphanumeric key with a maximum of four characters for a sales document type and a textual description for the key.
2. Maintain the specifications on the detail screen according to your requirements. -
Unable to assign new sales document type to sales area.
Hi,
I had created new sales document type. While I assigning to sales area it showing error " Define <XXX/XX/XX > first as a general sales area." I had already created sales area in enterprise structure. I had configured Combine sales org, dist channel & division also. Kindly help me on this.
Regards
NagendraHi,
I hope you have maintained following Settings:
SPRO --> IMG --> Enterprise Structure --> Definition --> Sales and Distribution --> Define, copy, delete, check Sales Org
SPRO --> IMG --> Enterprise Structure --> Definition --> Sales and Distribution --> Define, copy, delete, check Distribution Channel
SPRO --> IMG --> Enterprise Structure --> Definition --> Logistics - General --> Define, copy, delete, check Distribution Channel
SPRO --> IMG --> Enterprise Structure --> Definition --> Logistics - General --> Define, copy, delete, check Plant (In case)
SPRO --> IMG --> Enterprise Structure --> Assignment --> Sales and Distribution --> Assign Sales Org. to Company Code
SPRO --> IMG --> Enterprise Structure --> Assignment --> Sales and Distribution --> Assign Dist. Channel to Sales Org.
SPRO --> IMG --> Enterprise Structure --> Assignment --> Sales and Distribution --> Assign Divsion to Sales Org.
SPRO --> IMG --> Enterprise Structure --> Assignment --> Sales and Distribution --> Set up Sales Area
SPRO --> IMG --> Enterprise Structure --> Assignment --> Sales and Distribution --> Assign Sales Org.-Dist. Channel-Plant
SPRO --> IMG --> Sales and Distribution --> Master Data --> Define Common Dist. Channel
SPRO --> IMG --> Sales and Distribution --> Master Data --> Define Common Division
SPRO --> IMG --> Sales and Distribution Channel --> Sales Document Header --> Define Sales Doc. Type
SPRO --> IMG --> Sales and Distribution Channel --> Sales Document Header --> Define No. range Sales Doc.
SPRO --> IMG --> Sales and Distribution Channel --> Sales Document Header --> Assign Sales Area to Sales Doc. type
Best Regards,
Amit -
Distribution Channel Vs Sales Document Type
Dear All,
I have a confusion over my configuration process. My customer has the following types of customers:
1) Distributors, 2)C&F, 3)Institutional Sales, 4)Modern Sales, 5)Employee Sales, 6)Scrap Sales, 7)Sale of raw materials and 8)Exports.
Now I have an option of either creating 8 distribution channels and maintain one Sales document type or I can define one Distribution channel and define 8 sales document types.
My requirement can be achieved by both means but I wish to know which would be a better approach. Whether creating multiple Distribution channels or creating multiple sales document types. Can you please suggest me a better method among the two with advantages and disadvantages if possible?
As far as pricing condition records are concerned, I anyways have to maintain in the key combination either sales document type or distribution channel. So i am a little confused over which is a better approachIn normal cases, we would be having different sales areas for the following
1) Domestic
2) Exports
3) STO
4) Institutional
In fact, some clients would like to have Domestic OE and Domestic Retail since predominently, they cater to these segments and would like to have reports based on these. In my earlier project, they had gone for even Exports OE and Exports Retail due to the fact that their major sales is exports.
In your case, first decide whether to go for a seperate sales area or sale order type depending upon the volume of business the client would do. If the sale is going to happen only occasionally in any of the above, then have one sales area called miscellaneous sales.
As for as possible, have the document types to the minimal for better performance.
thanks
G. Lakshmipathi -
Billing document should not be cancelled after creating return sales order
Hi All,
Billing document should not be cancelled after creating return sales order with reference to billing document. Please suggest configuration settings on the same.
Sudheer.Hi,
In SAP, when the sub-sequent document is existing , we can not cancel the preceeding document. Therefore if you want to cancel the billing document you need to calcel the documents which are created with reference to that.
Check and confirm.
Regards,
Ravi Duggirala -
Sales document type restriction to create sales order
Hi Frinds,
My client has one requirement ...they have different sales document type. For sales document type free of charge delivery they want only some authorised person should be able to create sales order. Is it possible to set the authorisation to create sales order according to sales document type.
Regards
SVYes,
As already suggested, it is very well possible to restrict the user for the use of certain sales document type from basis.
& to add to the above,
Create Z* table with Sales Org + Doc type = UserID.
call this table in VA01 transaction & write piece of coding , if current USerID have entry in this table with the said combination - should not allow to proceed further.
without any basis involvement also you can ahieve your requirement.
Note: Sales Org is used for validation purpose only.
Regards,
Reazuddin MD -
What is the need of creating partner functions for sales document type.
Hi SAP (SD-GURUS),
Actually we create partner functions before creating customer ex: sold to party, ship to party, bill to party, and payer.
These partner functions are going to be copied into sales order while processing sales order.
Again what is the need of creating partner functions for sales document type.
Thanks&Regards
sreenivas peruruThere are some Partners you could enter at Sales ORder Level. E.g. Sales Person, Employee Responsible, Forwarding Agent, Broker, etc.
Thus these partner Determination need to be carried out at Sales Order Level & not at Customer Master level.
So we have to configure partner Determination for various levels e.g. Customer Master, Sales Order, Delivery level etc...
Hope this helps...
THanks,
Jignesh Mehta -
Issues in creating Sales Document Type
I am creating a new Sales Document Type, but the problem is this that the "Probability" &
"Incompl. Proced" fields are disabled and I am unable to enter record in this field , please help me out that how can I enter values in these fields.Hi shadab ali
You will be configuring the Incompletion procedure in SPRO->basic functions->Incompletion log procedure.
There to your sales document type an incompletion log will be assigned and that incompletion log will be getting grayed out. So if you want to change you need to change in in Incompletion log procedure. And the probability will be getting grayed out as it is determined by the Sales document category .That is the reason if you see for document type IN the probability will be different and if you see for document type QT probability will be different but if you see for document type OR the probability will be 100%.Generally it gets copied from the CMR also.
Regards
Srinath -
Immediate Transfer Order Creation not occuring for Sales Document Type
Hello gurus,
I have a situation where a transfer order is not being created immediately for a specific sales document type.
Here is an example document flow of a desired scenario where the system is working:
Sales document type: ZOR
> Delivery type: LF
> WMS transfer order
The Item Category in this scenario is TAN.
Here is an example of the document flow in the current scenario where the system is not working:
Sales document type: ZPRD
> Delivery type: LF
The Item Category is also TAN in this scenario. The only identifiable difference in these scenarios is the sales document type. For the ZOR SaTY, a Transfer Order prints immediately once the delivery is created. For the ZPRD SaTY, a Transfer Order needs to be manually created after delivery creation.
Is there a configuration setting that is controlling this? Any help would be greatly appreciated.Thank you very much for the link. When I insert the WMTA output type in the delivery output header, the Transfer Order is automatically created.
The problem I'm running into now is the configuration setting that controls this. I thought I figured it out when going to this IMG path:
SAP Customizing Implementation Guide --> Logistics Execution --> Shipping --> Basic Shipping Functions --> Output Control --> Define Print Parameters Shipping
When selecting the Delivery Note, the shipping point I was using was not configured in this location. I added the shipping point into this transaction, saved, and created a new order & delivery. However, the WMTA output type still was not automatically inserted into the delivery when saving. Is there another location I should be looking to fix this so that when I enter an order with a particular Shipping Point, the WMTA output type automatically appears in the delivery? -
Hi
i created a ALV and the output is displayed properly .then i added a field sales document type ,the problem i face is that after declaring, the output is displayed without any values
i like to know how to solve the problemHi
checked it and everything is fine.but i think the problem is in Select statement.the following is the select statement
SELECT VBRKVBELN VBRKKNUMV VBRKFKDAT VBRKWAERK
VBRKKURRF VBRKKUNAG VBRK~FKART
VBRPPOSNR VBRPNETWR VBRPFKIMG VBRPMATNR
VBRPMATKL VBRPVGBEL VBRPWERKS VBRPARKTX VBAK~AUART
INTO CORRESPONDING FIELDS OF TABLE ITAB
FROM VBRK
INNER JOIN VBRP
ON VBRKVBELN = VBRPVBELN
INNER JOIN VBAK
ON VBRKVBELN = VBAKVBELN
WHERE VBRK~VBELN IN VBELN
AND VBRK~FKART IN FKART
AND VBRK~FKDAT IN FKDAT
AND VBAK~AUART IN AUART
AND VBRP~MATKL IN MATKL
AND VBRP~WERKS IN WERKS
AND VBRK~FKSTO NE 'X' . -
Sales document type - field indicator
Hi,
In transaction VOV8 for sales document type, there is a field 'Indicator'.
What is the function of this field? There is no help associated for this field.
ThanksAs F1 help indicates this field is only for display in TVAK table.
So, it means if you are selecting this indicator, a program associated with this indicator would be running.
This indicator is used in certain order types only
for example
Order type RA - Repair order is assigned indicator F (you can also look for other order types and indicators assigned to them).
If you create a order with sales document type RA, you would notice certain changes when compared to regular sales order type OR.
The most prominent is button Repairs.
There may be others but you could check for them.
You can play around and assign indicator F to order type OR.
You would see that OR screen now resembles the screen order type RA. It has Repairs button associated with it.
In short, if you assign indicator to sales order type, it runs a program associated with it. The SAP program is SAPL080O. -
Unable to create a sales document
Hi frns,
while creating sales document (order) an error poping up saying No customer master record exists for Sold to Party.. Pls advise how to solve da above
regards,
kkThere is a possibility that a Customer Master record is not created, or if it is created, it may not be created in the required Sales Area. Please create Customer Master Data in XD01 & after that create Sales Order. It certainly shoule create Sales order. Also check your configuration for SD:
SD Configuration:
Enterprise Structure:
1. Maintaining Sales Organization
Sales Organization is an organizational unit responsible for the sale of certain products or services.
IMG -> Enterprise Structure -> Definition -> Sales and Distribution -> Define, copy, delete, check Sales organization
2. Assigning Sales Organization to Company Code
This assignment ensures all the sales made through this Sales Organization are accounted for in the assigned Company Code (Company Code is created by FI Consultant).
IMG -> Enterprise Structure -> Assignment -> Sales and Distribution -> Assign Sales Organziation to Company Code
3. Maintaining Distribution Channel
Distribution Channel is the way, in which Products or Services reach Customers.
IMG -> Enterprise Structure -> Definition -> Sales and Distribution -> Define, copy, delete, check distribution channel
4. Assigning Distribution Channel to Sales Organization
This assignment ensures, a Sales Organization can supply Materials to Customers through this Distribution Channel.
IMG -> Enterprise Structure -> Assignment -> Sales and Distribution > Assign distribution channel to sales organization
5. Maintaining Division
Division is a way of grouping materials, products, or services.
IMG -> Enterprise Structure -> Definition -> Logistics - General -> Define, copy, delete, check division
6. Assigning Division to Sales Organization
IMG -> Enterprise Structure -> Assignment -> Sales and Distribution -> Assign division to sales organization
7. Setting up Sales Area
All the sales are made from a particular sales Area. For creating a Sales Order Sales Area is compulsory.
IMG ->Enterprise Structure -> Assignment -> Sales and Distribution -> Set up sales area
8. Assigning Sales Organization- Distribution Channel- Plant
Plant is created ny MM Consultant.
IMG -> Enterprise Structure -> Assignment -> Sales and Distribution -> Assign sales organization - distribution channel - plant
9. Define Shipping Points
Shipping Point is the Organizational element, which is responsible for shipping the Materials to the Customers.
IMG -> Enterprise Structure -> Definition -> Logistics Execution -> Define, copy, delete, check shipping point
10 Assigning Shipping Point to Plant
This assignment ensures that goods from different Plant can be dispatched from different Shipping Points.
IMG -> Enterprise Structure -> Assignment -> Logistics Execution -> Assign shipping point to plant
Note: Ensure to do the undermentioned configuration also though it is not in Customizing node of Enterprise Structure.
11. Defining Common Distribution Channels for Master Data
Use
The purpose of this activity is to define distribution channels which have common master data..
Procedure
Access the activity using one of the following navigation options:
IMG Menu -> Sales and Distribution -> Master Data -> Define Common Distribution Channels
Transaction Code: VOR1
12. Defining Common Divisions for Master DataUse
The purpose of this activity is to define distribution channels which have common master data..
Procedure
Access the activity using one of the following navigation options:
IMG Menu -> Sales and Distribution -> Master Data -> Define Common Division
Transaction Code: VOR2
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.
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.
Normal Sales Order Cycle:-
Step 1: Sales Document Type
IMG > Sales and Distribution > Sales > Sales Documents >
Sales Document Header:
1. Sales Document Type:The sales document types represent the different business transactions, such as Inquiry, Quotation, Sales Order, etc. To create new sales order type, always copy as with reference to similar sales order. If possible use standard sales order.
2. Define Number Ranges For Sales Documents: Maintain number range with discussion with core team.
3. Assign Sales Area To Sales Document Types:
A. Combine sales organizations / Combine distribution channels / Combine divisions: Ensure to maintain these, else Sales Order creation will give error.
B. Assign sales order types permitted for sales areas: Assign only required Sales Order Types to required Sales Area. This will minimize selection of Sales Order Type as per sales area.
Sales Document Item:
1. Define Item Categories: If possible use Standard Item Category. Incase if required to create new, copy as from standard & maintain New.
2. Assign Item Categories: If possible, use standard. Formula for deriving item category: Sales Document Type + Item Category Group + Usage + Higher Level Item Category = Item Category
Schedule Line:
1. Define Schedule Line Categories: If possible use Standard Schedule Lines. Incase if required to create new, copy as from standard & maintain New.
2. Assign Schedule Line Categories: If possible, use standard. Formula for deriving Schedule Line: Item Category + MRP Type / No MRP Type.
Step 2:
IMG > Logistic Execution > Shipping > Deliveries >
1. Define Delivery Types: If possible use Standard Delivery Type. Incase if required to create new, copy as from standard & maintain New.
2. Define Item Categories for Deliveries: If possible use Standard Item Categories for Delivery Type. Incase if required to create new, copy as from standard & maintain New.
3. Define Number Ranges for Deliveries: Ensure to maintain number range.
Step 3:
IMG > Sales and Distribution > Billing >
1. Define Billing Types: If possible use Standard Billing Type. Incase if required to create new, copy as from standard & maintain New.
2. Define Number Range For Billing Documents: Ensure to maintain number range.
3. Maintain Copying Control For Billing Documents: Maintain relevant copy controls such as Sales Order to Billing, Deliver to Billing, etc.
The configuration differs from scenario to scenario & requirement of the client.
Regards,
Rajesh Banka
Reward point if useful. -
Problem in creating a sales document
Hi,,
I am creating a sales document programatically by the FM BAPI_SALESDOCU_CREATEFROMDATA1 for tht i have desigend ny selection screen in tht my requirement is i will not give item category for tht i have to quiery for given material and for given plant i have to fetch itcat plz help me in writing this quiery
vbap table is not coreect as it will store data after complettion of sales document
but here i want quiery to create a sales document it self
i have seen in transaction VA01 ity is getting data from t184 for itcat plz help me in writing this quiery
for good answer i will reward pointsYou can use the t.code SHD0, choose your transaction variant here, further choose your screen variant.
Next select your screen variant and in the Menu bar select Variant> change with processing>Make repairs in foreign namespaces only if they are urgent> Continue(Enter)>again 'enter'>Object can only be created in SAP package>continue(enter)> Exit and save >This variant contains other screens, adopt these as well?>enter>enter> scroll down to the entry make the necessary changes and save.
The system will prompt to assign a package and request enter the necessary values.
Your issue is sorted!!
And further to your query for minimum price PMIN refer to my answer, you will not have to maintain any condition record or the price entered here does not reflect in any other document.
Regards,
PATHIK -
Billing block for customer for sales document type OR
Hi
I want to block a customer for a particular sales document type OR
How to do it?
RegardsHi Nikhil
There is a field called "Check Partner Auth.", but it is necessary to create the order from a contract. This field is in sales document customizing VOV8.
SAP Documentation:
Check partner authorizations
This check determines whether a partner is authorized to release against a contract.
Procedure
Here you can specify whether the check is to be performed against the partners in the contract or the partners in the customer hierarchy. If you do not want the check to be performed, leave the field blank.
When you create a release order for a contract, the system determines whether a partner is authorized to release against the contract. The check is performed at header level. Depending on the rule you enter in this field, the system checks against one of the following:
Partners in the contract
If the partner has the partner function AG (sold-to party) or AA (sold-to party authorized to release) in the contract, the system accepts the partner as the sold-to party for the release order.
Partners in the hierarchy
If the sold-to party of the contract is at a higher level in the customer hierarchy to the partner who wants to release against the contract, the system accepts the partner as the sold-to party for the release order.
Note
If you create a contract with reference to another contract, the system does not run a check and it copies all the partners created in the target contract. If you do not want it to do this, use copying control in Customizing to change it.
Regards.
Mikel -
Two different billing document types for 1 sales document type.
Hi Gurus,
I have a requirement , wherein our client is having counter sale.
He is using one sales doc type , and while creating a order , he is manually adding payment terms.
Requirement is , if the payment terms are cash, billing doc type created later on should be one , else during credit sales , billing document type should be different.
As per my understanding this is not possible.
Want to know if anyone has some different thought on this.
Thanks in advance
Nilesh.Dear Nilesh,
There two options you can look in to
One option is
1.You can define different sales document types for cash and credit.
2. You can define two different billing documents.
3.Do the copy control settings for each combination
Cash sales order >Delivery>Cash invoice
Credit sales order >Delivery>Credit invoice
Second option is
1. You can maintain single sales document for both the processes.
2.Define two different billing types then do the copy control settings for both billing types.
But in this option user need to select the billing type manually based on the process while creating billing document.
I hope this will help you,
Regards,
Murali.
Maybe you are looking for
-
AQ Adapter: Invalid UTF8 encoding.
Hello, I am using the data type XMLType to enqueue data from a database to a BPEL process to integrate with other systems. We are using the AQ Adapter to receive messages from BPEL. For the most part it works, but when we are receiving multiple messa
-
How do I turn on sound alert for calls but turn off sound for txt
At night, I want to be able to hear if I get a call, but I do not want to hear if I get a txt mssg. I went into setting/txt/sounds and turned it off, and had a ring tone selected for calls, but when I get calls I do not hear the ring tone.
-
Maverick OSX: Memory use is increasing without running programs
I noticed that under Mavericks, my iMac is getting slower and slower. So I opened the Activiy Monitor to see what was going on. It appears that the amount of used Memory is increasing without that I even run 1 single program. While writing this post,
-
IPhoto doesn't load after installing iLife '11
I needed to install iDVD off the iLife '11 disk I had, and it seemingly installed a previous version of iPhoto. How can I restore the iPhoto app that came with the MacBookPro?
-
Url connection refused to site
Hi, I was using a program to connect to a website to pull down data and store in a file. Now I'm getting the following error: java.net.ConnectException: Connection refused: connect at java.net.PlainSocketImpl.socketConnect(Native Method) at