Error : pricing structure for doc type

hi gurus,]
while creating document type"RAILWAY FREIGHT" i have got an error that "CHANGES IN THE PRICING STRUCTURE FOR THE DOCUMENT TYPE RAILWAY FREIGHT PO"

Hi
The statement doesnt look like an error, was it an information message?

Similar Messages

Changes in the PRICING STRUCTURE FOR THE DOCUMENT TYPE

Hello Gurus,
What is pricing structure?
and what is meant by changes in pricing structure for the document type.
Could anyone let me know about pricing structure and changes in Pricing structure for document type.
prashant

Hi Prashnat,
In SAP Pricing works on Condition Techniqe.
Condition Technic consits to following things.
1.Condition Tabels ( Assigned to Access Sequence )
2.Access Sequence ( Assigned to Condition Types)
3.Condition Types ( Assigned to Pricing Procedure)
4.Pricing Procedure
5.In Pricing Procedure Determination will be assigning as fallows:
Sales Org + Dist Channel + Division + Document Pricing Procedure + Customer Pricing Procedure + Pricing Procedure.
Based on this the Pricing will be takes place in the system.
Hope this Clarifies your Doubts and Please Reward If Really Helpful,
Thanks and Regards,
Sateesh.Kandula

Does anyone know the pricing structure for Digital Marketing Suite?

Does anyone know the pricing structure for Digital Marketing Suite? I asked for info but no one ever got back to me. I don't want to waste anyones time if it's too expensive so I'd like to know up front what the fees/package rates are.
Thanks.
Peter Marino
Owner of an
SEO Comapny in NYC

This is the top story at this writing at AppleInsider:
Like the updated mid-2014 13-inch MacBook Pro with Retina display, Apple's latest 15-inch notebook brings slightly speedier Intel processors. But with memory, graphics and design all carried over from last year, the most substantial change is a $100 price cut.
http://appleinsider.com/articles/14/09/07/review-apples-mid-2014-15-inch-macbook -pro-with-retina-display

REPORT-TOTAL GR VALUE FOR DOC TYPES MONTHWISE

Dear Experts,
Please help me out for finding how to see the total value of GR for doc types NB and the Assets monthwise..

Hi,
Use ME2L or ME2K standard report.
In ME2L report enter the Purchasing org, Scope of list (ALLES), Plant, Account Assignement category A, Document date.
In ME2K you can see the report for individual asset.
Regards
Karthick

Error: Illegal syntax for elaborated type specifier

Hi ,
I am using Solaris 8 with SunStudio8 C++ 5.5 compiler
I have defined following lines in my header file msgg.h
typedef class DIMessageStringBase<char> DIMessageString;
typedef class DIMessageStringBase<UChar> DIMessageStringU;
On compilation I am getting folowing error in above header file
"msg.h":Error: Illegal syntax for elaborated type specifier
-riaj

Just remove keyword 'class'.

Error during search for movement type (953)

Hi All,
When I'm trying to issue goods to an internal order, I get the below error
Error during search for movement type (953)
The explanation is as follows
The movement type of the warehouse system and certain parameters are assigned to each movement type of the inventory management system
In this case no movement type of the warehouse management system was assigned to the inventory management movement type used by the paramaters enclosed in parantheses in the eror message.
Is there some config missing in this case?? Please let me know how to overcome this error
Regards,
Ashwin

when you create new movement types in MM, then you certainly have to create WM movement types too, if you want use the new movement types to post at a warehouse managed storage location.
This customizing needs to be done in IMG > LE > WM > Activities > transfers > define movement types
and
IMG > LE > WM > interfaces > inventory management > define movement types

OMB05602: An unknown Deployment error has occured for Object Type Deploymen

I was deploying a process_flow package here in named "PF_LOAD", then the following error occured.
OMB05602: An unknown Deployment error has occured for Object Type DeploymentContextImpl.generate WBGeneratedObject[] is null or length 0 for PF_LOAD.
Does anyone know what this error means or what possibly caused it?
So

Hi David
OWB version 10.2.0.3.0
This is what I cought from the log when tried to deploy the process flow via OMB+
OMBCREATE TRANSIENT DEPLOYMENT_ACTION_PLAN 'DEPLOY_PLAN_PROCESS_FLOWS'
Action plan DEPLOY_PLAN_PROCESS_FLOWS created.
OMBALTER DEPLOYMENT_ACTION_PLAN 'DEPLOY_PLAN_PROCESS_FLOWS' ADD ACTION 'PF_LOAD_PROCESS_FLOW_PACKAGE_DEPLOY' SET PROPERTIES (OPERATION) VALUES ('REPLACE') SET REFERENCE PROCESS_FLOW_PACKAGE 'PF_LOAD'
Action plan DEPLOY_PLAN_PROCESS_FLOWS altered.
OMBDEPLOY DEPLOYMENT_ACTION_PLAN 'DEPLOY_PLAN_PROCESS_FLOWS'
OMB05602: An unknown Deployment error has occured for Object Type DeploymentContextImpl.generate WBGeneratedObject[] is null or length 0 for PF_LOAD.
When I viewed via the control center jobs detail window, it is not even logged there.
Cheers
So

How to configure F.62 for Doc Type SAP19?

Team,
I want to configure F.62 for doc type SAP19. Could you please list steps - (I am not very familiar with SAPcript)
Thanks
Release 4.7

Hi Naved,
Go to the configuration (TC SPRO) in Financial Accounting -> AR and AP -> Business Transactions -> Outgoing Invoices -> Carry Out abd Check Settings for Correspondence.
There, you need to assign your custom Layout for the Correspondence Type (SAP19).
Cheers,
Bhanu

Assinment of pricing procedure to doc type

Hi friends,
I am new to MM , how the pricing procedure is assigned to doc type, or how the pp is triggered in PO.
Thanks
madhu

Hi Madhu Sudan,
Pricing Procedure as you know is one and the same as calculation schema.
To administer the PP i.e. Determination of Calculation Schema for PO you will have to go to the transaction SPRO---SAP Reference IMG
Follow the node
Materials Management-Purchasing-Conditions-Define Price Determination Process-Define Calculation Schema.
Once you are there In the calculation schema (pricing procedure), you specify which condition types are to be taken into account in which sequence
Now coming to your query,
1) Assignment a Calculation Schema (PP) to Doc type
-- Remember It is not possible to assign PP to Doc type
2) Trigerring of PP in PO
-- Follow these underwritten simple steps:
i. Define a schema group for vendor under the node> Materials Management-Purchasing-Conditions-Define Price Determination Process-Define Schema group. You will have to assign this same schema group in the relevant vendor master record.
ii. Define a schema group for Purchasing organisation under the node> Materials Management-Purchasing-Conditions-Define Price Determination Process-Define Schema group. & assign it to the relevant Purchasing Organisation in the same step.
iii. Once this is done you have to Determine Calculation Schema for Standard Purchase Order under the node>Materials Management-Purchasing-Conditions-Define Price Determination Process-Define Schema Determination. In this step you assign Calculation Schema to a combination of Schema Group (Purchasing Organisation) & Schema Group (Vendor).
iv. Conclusion: During the time of making a PO; Shema Group of Vendor is picked from the relevant Vendor Master Record, Schema Group of Purchasing Organisation is picked from Customisation (where you assigned it) & A Calculation Schema is triggered for the combination of these two Schema Groups (PP that you defined in step iii)
Hope this explains it, for better understanding please read the IMG activity documentation for each activity.
For any further doubts please reply.
Regards,
Prithviraj

Pricing structure for vendors

Dear friends,
I want to define a pricing procedure for the following scenario pls help:
For local vendors
Total price = basic price + discount + freight cost
For foreign vendors
Total price = basic price + discount + freight cost + Customs
Tks
Kali

Hi,
The Pricing Procedure assigned to a vendor has a calculation schema attached to it. This schema defines the various conditionsu2019 pre-requisite, calculation & sequence in the PO. Generally, only one type of pricing procedure is followed for all the vendors
Select the Pricing Procedure which is the standard and copy it and create our own pricing procedure.
Highlight it and double click the Control icon in the LHS screen.
We can see that there are 16 columns in the pricing procedure, these are going to be used by the system to control the condition types.
The detail description of each column is given below.
Step:
Number that determines the sequence of the conditions with in a procedure.
It indicates the position of the condition type in pricing procedure.
Ex.: 10, 15 etc.
Counter:
System uses the counter to count the steps and also it can be used to count mini steps of same condition types. So that number of steps can be reduced in the pricing procedure and hence enhancing the system performance.
Access number of the conditions with in a step in the pricing procedure.
During automatic pricing, the system takes into account the sequence specified by the counter.
Condition Type:
It represents pricing element in pricing procedure as a base price, discount, freight and tax.
The condition type is used for different functions. In pricing, for example, the condition type lets you differentiate between different kinds of discount; in output determination, between different output types such as order confirmation or delivery note; in batch determination, between different strategy types.
Ex.: PR00 - Price
K004 - Material Discount
K005 - Customer/Material Discount
K007 - Customer Discount.
Description:
System copies description of condition type from its description (V/06).
From and To:
1.From: This can be used as a base to the condition type for calculating further value.
1.{+}From and To: + The range between the steps from and to can be used to specify the range between same condition types. So that depending upon the condition type, the system deducts or adds the total value of those condition types from specific common source.
Manual:
This indicator specifies whether the specific condition type can be determined manually during sales order processing.
If we check the box then the entry is going to be manual, if we uncheck it, it is going to be automatic.
For Base Price and Taxes, the entry should be automatic.
For Discounts and Freights, The entry should be manual.
If we check the box, in VA01 when we go to conditions at the header/item level, the condition type will not be listed. If we require we will have to manually enter it.
If we un-check the box, in VA01 when we go to conditions at the header/item level, the condition type will be listed.
Mandatory:
This indicator specifies that particular condition type is mandatory in the pricing procedure.
If we check the box, then in VA01 at the header/item level in the conditions tab, if we delete the value in the condition type and try to save the document then system will not allow us to do it and throws an error.
If we uncheck the box, then in VA01 at the header/item level in the conditions tab, if we delete the value in the condition type and try to save the document then system will allow us to save it, without giving any error.
Mandatory check box should be checked in condition types which are compulsorily required in pricing procedure. Ex.: PR00, MWST.
If the condition type is checked with mandatory option, then value should be maintained for that condition type, otherwise the system will not allow the user to process the document.
Statistical:
This indicator if it is activated will not allow the value of the condition type to be taken into net value calculation.
It is used only for information purposes only.
This indicator causes a surcharge or discount to be set in the document statistically (that is, without altering the value).
This is commonly used for condition types
SKTO - Cash Discount
VPRS - Cost (Moving average price/Standard Price).
Print:
The value of this field specifies whether line item can be printed or not in the sales document and at what level it is to be printed.
Subtotal:
The value of this field determines where the values of subtotals to be captured i.e. in which table and which field.
Controls whether and in which fields condition amounts or subtotals (for example, a customer discount or the cost of a material) are stored.
If the same fields are used to store different condition amounts, the system totals the individual amounts.
These condition amounts or subtotals are used as a starting point for further calculations. You may, for example, want a subtotal of all the discounts included in the pricing of a sales order.
Requirement:
It is a routine that is written by an ABAP consultant according to the business requirement.
By defining Requirement in condition technique we can restrict the access of condition type.
To understand the concept, we will take the example of the Rebates. Rebates are to be included during the billing document processing and not in the sales document processing. As rebates are given on the delivered quantity and not on the ordered quantity (in case of cut-off period for rebates).
For rebates we use the condition types BO01 to BO05, and in the Requirement column we give the value 24 which is "Only in Billing Document".
This Requirement will ensure that these condition types will appear only during the billing document processing.
If new Requirements are to be defined we follow the procedure given below.
Go to T.Code: VOFM. - Maintain Requirements & Formulas
Click on the "Requirements" in the top menu and then click on "pricing".
We have a list of requirements, we can ask ABAP consultant to create new requirement based on the client requests.
And we assign the application type like V - Sales/Distribution etc.
AltCty - Condition formula for alternative calculation type:
It is again a Routine that is written by ABAP Consultant.
It is an alternative formula for the condition type that can be used instead of standard formulas.
For example, let us take the Profit Margin which can be both + / - , so here this routine will help us in generating the value which can be either + or -. Profit margin is not a condition type so it cannot be classified as +ve or -ve in the V/06.
Ex.: 950 0 Profit Margin 11.
So we assign 11 - Profit Margin.
If new routines are to be defined we follow the procedure given below.
Go to T.Code: VOFM. - Maintain Requirements & Formulas
Click on the "Formulas" and then on the "Condition Values".
We have a list of routines, we can ask ABAP consultant to create new routines based on the client requests.
And we assign the application type.
AltCBV - Alternative formula for condition base value:
Formula for determining the condition basis as an alternative to the standard.
It is again a Routine that is written by ABAP Consultant.
It is used as a basis to calculate value of the condition type instead of using it from the "FROM" column.
Ex.: Freight - KF00.
Freight is calculated based on weight, volume etc. and not on the base price. In pricing there is no entry of weight from which the value can be referred like we do for discounts using base price. We have to get the value from the Material master.
In this column we can mention the value as 12 - Gross Weight or 13 - Net Weight.
During pricing, the system will consider the value that is mentioned in this column and determine the freight based on this value.
Suppose we have Net weight: 100 kgs and Gross Weight: 150 kgs. And if we mention 13 in this column then the Freight condition KF00 will be calculated using the weight as 100 kgs.
AcyKy - Account Key/ Accrls - Accruals:
The values of the Sales Revenues, Sales Deductions, Freight Revenues, Tax Revenues, and Rebate Accruals etc. are going to be posted in the respective G/L accounts in Fi Module.
In order to do this we assign account keys/ accruals to the different condition types based on their classification. The classification shown below.
ERB Rebate sales deduct.
ERF Freight revenue
ERL Revenue
ERS Sales deductions
ERU Rebate accruals
For Ex.,
For all Price condition types like PR00 etc. we assign ERL - Revenue.
For all Discount condition types like K004, K005 etc. we assign ERS - Sales Deductions.
For all Freight condition types KF00 etc. we assign ERF - Freight Revenues.
For all Rebates condition types BO01 to BO05 we assign in Account key ERB - Rebates Sales deductions and for Accruals ERU - Rebate Accruals.
This account keys and accruals are in turn assigned to respective G/L accounts. So the system posts respective values in respective G/L accounts in Fi-Co Module.
This also one of the areas of SD - Fi Integration. SD consultants assign the account keys and Fi Consultants assign the respective G/L accounts in T.Code:VKOA.

FB05 - trans to be processed and first line item PK for doc type

Hi all,
Me quite confused of the entry for the following document type in FB05
DG - cust credit memo
DR - cust invoice
SA- gl acc doc
SB - gl acc posting
KG - vdr credit memo
DZ - customer payment
Need the help to let me know for document type above, what radio button to choose in transaction to be processed and also what posting key use at first line item.
Also if i choose the wrong transaction to be processed radio button, any impact?
thanks
rgds

Document type is primarily used to distinguish different various types of transactions. Ultimately, there are only two effects in accouting - debit and credit. Thus, doc type helps distinguish btw various types of accounting entries. It also controls certain field status while document posting and also drives the number range for the accounting document.
Posting keys determine whether a transaction will be a credit or a debit. They also have an influence over the field status of the document entry screen. Posting keys are broadly divided into those belonging to
Customer                             - Acct type C
Vendors                               - Acct type V
GL                                       - Acct type G
Fixed Assets                        - Acct type A and
Material Mgmt. transactions   - Acct type M
For each account type there are both debit and credit posting keys. You can clik on F4 on the posting key field and see the various entries. You will understand.
Thus, which posting key to enter depends on the transaction you want to enter.
Regards,

Validation for doc type for f-43

Hi,
I Have created a validation for document type sk for t.code f-43, while creating validation i have taken fb01 it is working fine for f-43 at the same time which is working for f-02 also it should not work for f-02.what to do please help me
Thanks and Regards
Radha

Hi,
Almost all FI transactions other than the clearing transactions, may apparently have different names like F-02, F-43 etc, but at the backend there is only one mother transaction code FB01. So any validation on FB01 will impact all FI t-codes.
I would suggest that you use document type in the validation, if you can have clear demarcation between the doc type used for different transactions.
Cheers.

Error :- No authorization for basic types (activity 01)

Hi Experts,
While trying something at the BW server i suddenly got the below error
I am getting the error when i am accessing the T-CODE RSA1.
Error :- You have no authorization for basic types (activity 01)
I checked the ids of my colleagues all are getting the same messages...
Regards,
RG

Hi,
1. Check in SU53 tcode
2. You are having RSECADMIN/PFCG tcode access?? If yes you can give authorisation for the same.
3. You dont have S_RS_ADMWB - authorisation
4. for your user id give this above authorisation
5. If you are unable to do the same, ask your basis team to give you the authorisation
refer this link- 1.http://help.sap.com/saphelp_nw70ehp1/helpdata/en/f3/291542e4b4df2ce10000000a1550b0/frameset.htm
2.http://help.sap.com/saphelp_nw70ehp1/helpdata/en/a4/1be541f321c717e10000000a155106/frameset.htm
Edited by: Asish Sahu on Apr 28, 2009 10:34 AM

Error :- No authorization for basic types

Hi Experts,
While trying something at the BW server i suddenly got the below error
I am getting the error when i am accessing the T-CODE RSA1.
Error :- You have no authorization for basic types (activity 01)
I checked the ids of my colleagues all are getting the same messages...
Regards,
RG

Hi,
analyze the missing authorization with transaction SU53 immediately when the error appeared.
Ask your system/authorization administrator to grant you the missing authorization.
Regards
Rainer

Material number is blank in FBL3N for doc type SA

Hi,
If posting is coming from SD or MM module, the material number is reflected in FBL3N for GL acct "Material price variance". But when the posting is coming from FI, the material field is blank.
But in another company code, when postings are from FI, the material field is correctly populated.
I have already checked and verified that BSEG-MATNR was defined as a special field. I have also ran RFPOSXEXTEND and BALVBUFDEL but the material field from FI posting is still blank.
The FI posting involves filling up the material or product number in the profitability segment amongst other fields and then system will do a derivation.
Can someone point me to the right direction on how to get the material field populated by an FI posting?
Thanks and regards,
Thess

Hi,
The material field should appear in FBL3N for all types of postings, provided it got populated. Can you please check, whether material field is getting populated in BSEG table for that document # ? If the material is not getting derived, then it won't appear in the report.
Best Regards,
Madhu

Error : pricing structure for doc type

Similar Messages

Maybe you are looking for