0DOC_CATEGR-Sales Document Category of Reference Doc. in Order Header

Hi,
I am extracting the standard datasource for Sales Order Header 2Lis_11_VAHDR to BW.I am getting error while loading data.I checked it in PSA there are around 30 records which were showing the error with the message
"Record 985 :Contents M from field VGTYP_AK(mapped to 0DOC_CATEGR) cannot be converted in type DEC ->longtext RSAR 198" and
"Error in an arithmetic operation in record 985 RSAR117".
I am not getting this error while loading the Order Item Data.
'M' is the Document Category of Reference Doc. in Order Header.For sales document type "RE".
In R/3 the reference was taken on Inv.No instead of Order number and also there is a User Exit written on MV45AFZZ program to check the referred quantities and also zero quantiity lines in case of back split.
As there is no customization done in BW and the only customization was in terms of an User Exit in R/3 please let me know what is the reason of this error.
Thanks in advance.
Venkat

Hi Venkat,
Assume the data mapping in transfer rule and update rule is correct
Maybe you can check the info object definition of 0DOC_CATEGR in your system. Based on the error message you mentioned below, it looks like 'data type' of the object concerned is NUMC? In our system it is CHAR (standard BC)...
Regards,
Lilly

Similar Messages

Document number and reference doc number

Hi All,
When i post a invoice through F-22 i get a document number.
1: Is this doc. number also called invoice number
2: What is reference document number (XBLNR field). From where does it get its value
What's the use of this reference doc. number and how different it is from doc. number
Thanks in advance,
Prashanth

hey,
1. It is the invoice no.
2. The reference document number is used as a search criterion when displaying or changing documents. In correspondence, the reference document number is sometimes printed in place of the document number.
Ex; Vendor send the invoice and it has a no. on it. You can use that no as document no and/or reference no when posting in the system. So when you do a search it is easy to pull the invoice based in this no.
Hope this helps.
Assign points if helpful

Conversion from 4.6C to ECC 6.0 issue with Sales Document Category K

Hello.
     My company is upgrading from a 4.6C system to an SAP ECC 6.0. We have batch management on for all materials. There was a bug in SAP 4.6C which allowed the creation of a Credit memo request, (SD Document Category H), and the user did not have to enter a valid batch as part of the creation process using VA01. The batch checking was skipped. This was not realized until the process failed in testing for ECC 6.0. These types of documents are create manually and via IDOC's.
     ECC 6.0 contains the fix for the bug and the check is now being invoked for batches OSS Note 740397 describes the bug and fix. Is there a way using configuration to have the batch check be turned off during credit memo request creation? In debugging the code this does not seems possible. It appears from the abap code this is not possible and based upon the Category H a batch is required. Just checking.
     I have change the SD Document Category to H*(Returns) and the Screen Sequence to be RE(Returns). The user and the IDOC can now enter existing batches and non existing batches. The problem now is the processing of the Orders IDOC is somehow not storing the quantity. I have debugged the IDOC processing, the IDOC is using call transaction, and I see the quantity is to be populated in the properly in the BDC table used by the call transcation. Yet it is not on the return delivery once the IDOC processes. Any idea why or which field from the IDOC should be populated? I am assuming that the processing of the Credit memo request and the Return is different from an IDOC perspective and will require different fields to be populated. Not sure just a thought.
     Any help would be greatly appreciated.
Regards,
Bob

Hi Mani,
As long as it is a warning u dont need to worry.Check if the search help is working
Regards,
Amit

Condition types doubling/tripling/...when sales documents created with reference to other documents

Hi,
When I create a sales order with reference to a Quote, the pricing condition types are duplicating. Same is happening when subsequent documents like Billing, credit memo request and credit memo are created. Particularly, the condition types are doubled/tripled/.... in the subsequent documents. Because of this, pricing net value is calculated wrong. For example, freight charges getting added twice. I searched the forum and found similar issue was discussed at Condition types - Doubling UP raised by forum member Sridhar Vijjhalwar, however there is no solution added in it.
Has any other member came across this issue and resolved?
I have checked the access sequence and exclusive indicators are checked. Copy controls are also checked, looked good and I tested by adding copying type D/G. Checked OSS note also and found one OSS note 1459807 - Invoice has missing/incorrect conditions when created from a sales order.
but it is not solving the problem either. Issue also elevated to SAP for their investigation. Our system is SAP ECC 6.0 - EHP6.
Quote Pricing:
Sales order Pricing:
I appreciate any pointers to resolve the issue.
Regards,

what was the scenario, and how did you replicate?
It is a configuration for a new project (France country), however we found that the same issue popping up for existing business processes also. As for replicating, we just tried the same procedures, the issue is found in subsequent documents.
If you have observed one notable thing is - all the condition types which duplicated were Z Conditions, and the standard conditions were never duplicated at least in my case.
In our case even standard condition types like MWST, SKTO, GRWR, VPRS also shows duplicating.
if you can throw about the business process?
As you have mentioned order created with reference to quote was only the straight forward scenario?
I tested other scenario also, like creating a sales order, then delivery and then billing. In this case in billing document, the condition types are duplicating. If I create a credit memo request against the billing document, then it further duplicating.
I am not sure what is causing this. I initially thought it may be copy control settings pertaining to the new project, however other business documents also has the same issue. Other business are using different document types.
Thanks for your follow-up.
Regards,

Mandatory field in sales document

Hello experts,
I'm working with CRM 4.0 SP08
How can I make mandatory some fields into CRM sales document ?
1 - Requested delivery date at header level.
2 - Reference date at header level.
How could I fill up theses fields automatically by default ?
Regards
Juan

Hi Juan,
If u want to make some fields mandatory in Sales doc, then u can use Incompleteness Check, follow below path:
SPRO->SAP Implementation Guide->Customer Relationship Management->Basic Functions->Incompleteness->Define Incompleteness Procedures
1) Create Incompleteness Group for Trasaction
2) Assign ur TransactionType to Incompleteness Group
3) Create Incompleteness Procedure and define fields which u want to make manadatory.
4) Determination of Incompleteness Procedure.
As Siddharth explained above used date rules in profile for u r date realted query.
Regards,
Dipesh.

Document flow for sales document

It is possible NOT update the document flow when i create sales document with reference to onther sales document?
Thanks.

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
Hope this can assist.
Thanks & Regards
JP

Link multiple sales documents to a credit memo

Hi,
Long time ago someone showed me standard configuration ( SPRO -Sales and Distribution -> Basic Functions) -Where a credit memo can be linked to multiple sales order/billing document.
In the credit memo screen, you enter multiple sales order/billing document in each row and corresponding credit memo in adjacent column.
Does anyone know this?
Thanks.

Hi,
If you want to link one credit memo with multiple sales/billing document
Then create credit memo with reference to previous document when you are on main screen of credit memo
Again go to SALES DOCUMENT >>> create with reference
then specify another previous document and click on copy the item from second previous document should be appear
Note : Due to system unavailable I am not tested this please try
As far as my understanding it will work if customer from previous document are same
kapil

Sales Document Type K with negative price

Hi
Please, I have the following error. I defined a sales document type ZS01 with sales document category "K - Credit memo Request".
When i create a sales order ZS01 and define price 1000 USD in PR00 condition type the price is converted to negative ( - ). I changed K for C (Order) and try again created another sales order and when I define the price 1000 USD in PR00 they no change
Why the price is changed a negative value in sales order with sales document category K?
Best Regards
Enrique

Hi Enrique,
There is nothing to do with the sales document category here.You can set that one to K only.
This setting is done in Condition type.
Goto V/06 T.Code or follow thw path:
SPRO>Sales and Distribution>Basic functions>Pricing>Pricing Control>Define Condition types>Maintain Condition types.
Here search for Pr00 using position option.Select that line and goto details.In Control data1 tab there is a field calles ad plus/minus.
For your case it might be set as "X".Remove that one.
Save.
Regards,
Krishna.

In accounting document ..field reference / assignment (invoice no) is empty

Dear all
I opened VF03 and open accounting document saw field reference / assignment (invoice no) is empty because of that field reference (invoice no ) display empty in FBL5N.
Sanj

Its a very basic question.
Based on your sales process.
Refer following copying control header you need to maintain reference & assignement number based on your business requirement.
For your reference.
TCODE
Sales Process
Assignment Number
Reference number
VTFA
order related billing
B-Sales order number
A-Purchase order number
VTFL
delivery related billing
B-Sales order number
A-Purchase order number
Regards
JP

Creating a Document Category

Hi SDNers,
We are running ECC 6.0/Funds Management with Former Budgeting.
When running FMMC to close Earmarked Funds, the program results in a short dump. When run in dialog mode, the following error message is displayed:
Document Type 11 is not defined for document category 001.
The procedure recommends going to Funds Management Customizing to define a document type for document category 001. When I go to the IMG, there is not an option for doc. catg. 001 and it will not let me create it.
I have two questions, if the document type is not defined for the document category, how can earmarked funds posting reflect this? Table KBLK shows the document type 11 assigned to document category 001.
The second question is how does one create a document category, so that Doc. Types can be assigned?
Thanks,
-Patrick

Patrick,
It sounds like you may have some kind of data inconsistency with this document. The earmarked funds document categories are not configurable. They are defined with the domain FMRE_BLTYP. The valid values are:
002     Funds transfer
020     Funds Block
030     Funds reservation
040     Funds precommitment
050     Funds commitment
060     Forecast of revenue
I would look in table TKBBA and see what category your document type 11 is tied to. If it's not 001 (which I highly doubt it is), then your data in KBLK is incorrect.
Hope this helps.
Thanks,
Todd

Reference Doc (Field - LFBNR) against IV cancellation - EKBE table

Hi,
We want to refer to table - EKBE, for getting a link between the original IV (Material Doc) with the cancellation (Material) IV Doc.
At my earlier site, our cancellation (Material) IV Doc was getting updated as a "Reference Doc" against the Original (Material Doc) IV doc. which was a easy way to identify a link between Original IV (Material) Doc. & Cancelled (Material) IV doc for ABAP development logic. Was that becuase of any user exit or development to update the "Reference Doc." field in Table - EKBE ?
Right now at our client, GR Doc (Material Doc) is getting updated as a "Reference Doc (Field - EKBE-LFBNR)" against all the material doc. pertaining to a particular P.O. in table - EKBE which require to give a different logic to identify the relationship between these 2 documents for ABAP development.
No question of giving a different logic but that was a easy way to identify the relatioship.
If possible, please confirm to me as which doc, system is referring as a "Reference Doc."
Is there any setting we do for updating the particular document as a "Reference Doc." in EKBE Table.
There is a SAP note about leaving the field "Reference Doc." as a blank field or updated with the Material doc.
But my point is that we want cancelled (Material Doc) IV as a "Reference Doc." against the original IV doc. to set a logic for ABAP development ?
Regards,
Shridhar

Hi,
No body is there who has handled in past such a requirement?
I want to substitute the Reference Doc. - (Field - LFBNR) of Table - EKBE with the cancelled IV doc (MIRO cancelled doc).
Purpose of this development is to identify the relation between Original IV (Material) Doc. with the Cancelled IV (Material) Doc.
This logic will help us in one of our ABAP development.
Regards,
Shridhar

Is it possible to create a Credit memo without reference doc

Hi,
I need to create a billing document (VF01) without passing the refernce document number. Is there any way to create this? While creating the billing document i just want to pass only items.
Thanks In Advance,
Regards,
Raj

the answer is that you can create a Credit Memo request (sales document) without a reference to a billing document. The settings for this are maintained in
SPRO>Sales and Distribution>Sales>Sales Documents>Sales Document Header>Define Sales Document Types
In the sales document type, the field that controls whether a reference document is necessary is in the General Control pane and is called "Reference Mandatory" - BEZOB
If that field is blank you don't need a reference number. You can also generate the actual Credit Note (billing document) without any problems. All accounting entries are carried out as normal.
SAP help says:
Reference mandatory
Indicates whether, when you create a sales document, a reference document is mandatory. If so, the indicator also specifies which type ofreference document you should use.
Use
When you try to create a sales document that has a mandatory reference document, the system automatically prompts you for the number of the reference document.

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

What are the Special Sales document types ?

Dear SAP Gurus
What are the Special Sales document types ?
Regards
ND

ND
Special Sales document types are :-
1.SO-Rush Order.
2.G2-Credit
3.RE-Return order
4.KN
5.RK-Invoice Correction request
Regards
Vivek

Debit Memo Request with Reference to Service Order

Hi Team,
I need to create the following business process
Service Notification -> Service Order -> Debit Memo Request -> Debit Memo.
I'm able to create the notification and the service order. However while creating the debit memo request with reference to the service order I'm stuck. Not sure where and how do I give the reference document number for the data to flow from the Service Order to Debit Memo Request.
Regards
Nadarajah Pratheb

Hi Nadarajah,
The following may help you.
1.Check the sales document category of the service order you are using.
2. Check which kind of document given in the with reference screen has the same sales document category.
3. For that document type, enter the service order as the reference.
4. Now you can see the details getting copied to the debit memo request.
5. Make sure copy controls are properly maintained from service order to debit memo request.
Please assign reward points if it helps.

0DOC_CATEGR-Sales Document Category of Reference Doc. in Order Header

Similar Messages

Maybe you are looking for