CK51N Valuation variant of the "ActivityTyes/Processes"

Hi Guys,
In the valuation variant of the "ActivityTyes/Processes", about the cost calculation of "Sales Order costing" (transaction CK51N), I set the strategy seq. 2 'Plan price as average for all fiscal year periods'.
I have some activities that have unit of measurement (technical field CKIS-MEEHT) = MS/MIN and MIS.
Does anyone know, firstly, how the system calculates the value of the activity, secondly, the exact formula or BAPI that the system uses?
Thanks and Regards,
Laura

Hi Laura,
every activity type has a unit of measurement (UoM) in its activity master data. The activity rate is planned based on this UoM.
'Plan price as average for all fiscal year periods' means for a given act. type XYZ with UoM MIS:
Period         Act. rate per UOM      total quantity planned
001-005      100 per 1 MIS            100 MIS
006-012      80 per 1 MIS              110 MIS
Its calculated like: (100 * 100 * 5 + 80 * 110 * 7) / (100 * 5 + 110 * 7) = 111600 / 1270 = 87,87 / MIS for every period in this fiscal year.
Best regards, Christian

Similar Messages

Version in Valuation variant

Dear all,
in OPL1, the standard sap valuation variant - under the activity type / process - there is a option called verion.
what is the use of this? Where i can use this option???
Could you kindly give me an example
Waiting for your valuabel reply
Regards
Elango

Hi,
in the valuation variant under "activity type/processes" you can enter the CO-version where the activity rates are taken from.
Example: If you want to see the cost estimation effect of different activity rates (from different CO-versions) create two valuation variants with the only difference that one variant picks the act. rates from version X the aother one from version Y.
Best regards, Christian

Valuation Variant - Quotation Price via Condition Table

Hi all,
Regarding cost estimate in SAP, there are valuation variants. The strategy sequence "Price from Purchasing Info Record" is one step in the material valuation strategy sequence of our valuation variant PP01. There is also a sub strategy sequence with this Puchasing Info Record Valuation called "Quotation Price via Condition Table".
What does the mean, where can I find this condition table and how will the price be calculated??? Can anybody help me please?
Thanks,
Anne

Create origin group via Tcode OKZ1 and then assign the conditions that you want to include in product costing in Tcode OKK4.
In OKK4 by clicking delivery costs or create new icon you will get a popupform which can be used to input chosen conditions as follows.
PB00 0 200 1000 1000 1000 PR01
We are using it to calculate material price excluding excise duty (sort of withholding tax which can be reclaimed so will not form part of material cost)

Costing variant/valuation variant

dear gurus,
    can any body explain the costing variants,valuation variant,costing sheet,costing type,how it is integrated in production order in controlling tab.can any body explains the customizing part of product costing and overview.
if any body is having the product costing material please send to [email protected]
    please through some light on product costing
                                                                        -gide

Hi,
Every cost estimate we create is based on the costing variant.
In the costing variant we define the control parameters and settings for costing
Settings contains info such as prices that will be used to cost the materials and activities
Control parameters are used for the automatic determination of of qty str ie Bom and Routing
Every costing variant contains a valuation variant and a costing type , date control , qty str control.
Valuation variant:
Valuation variant defines the price with which the material and activities are valuated
determines 1.which price is taken from material masterrecord to calculate the material cost
2.
which price is taken from cost center accounting to calculate the costs for internal activities
3. which price is taken from purchasing info rec to calculate the the costs for ext activities / subcontracting
4. which costing sheet is used to calculate the over head costs
Costing type:
costing type defines the valuation view to be costed and defines the purpose of costing.
Date control :
       controls the validity of the cost estimste , qty str date.
Valuation class:
For material costing the valuation class controls the cost element to which the planned cost of the material are assigned and the cost element under which the actual costs are updated when the material produced is delivered to stock
Valuation category:
specified the criteria according to which partial stocks are distinguished from one another
Price control indicator:
the price control indicator specifies whether the stock of the material is valuated with standard price or moving avg price
costing sheet:
            The costing sheet links all the functions for overhead calculation.
    In the costing sheet we determine the following
    1.The direct costs to which the over head is applied
    2.The condition under which the over head is applied
    3.Whether the over head is applied as a percentage basis or on a qty basis
    4.The amt of overhead percentage
    5.The validity period of the over head
    6.Which object is credited ( order , cost center) and which cost element in the case of actual posting
   We enter the costing sheet in the valuation variant in customising
Regards,
nandha

Process Chain got struck and not showing all the variants in the log view

Hi,
We have some process chains which are running daily.The problem here is that one of the process chains got struck at some point
and it is not showing all the variants in the log view but able to see in planning view.
Could any one please let me know why this is occuring.

Hi Ramanjaneyulu,
Thanks for the reply.
As you said,i clicked on the 'display message' but it is not showing any errors.It is showing
that the process completed successfully.
Thanks.

Strategies for valuation variant

Hi,
I am creating a valuation variant in Product Costing for standard cost estimation.
Could someone tell me what the most common strategies for materials, activities, subcontracting and ect. processing are?
I know that it depends on the agreement with client, but I don't have any information about the client needs, so have to do a standard, most common valuation variant.
Thanks,
Karol

Hi
General valuation strategies would be as follows
1) Material - Planned price, Std price, Moving avg price, Purchase Info records
2) Activity - Plan price for the period, Most upto date plan price
3) Sub Contracting - Effective price from purchase order, Net / Gross purchase order price
4) Ext Processing - Same as in 3
The above are general strategies - but also depends on various other parameters viz
1) Decision on activity pricing
2) Hw stable are material prices - it also depends on commodity types if u are
implementing for metals
3) Subcontracting strategies will work only if u hv subcontract situation. Here again u need to define a std price in the system and do sub contract product costing
4) External operation is used - if operations are outsourced to vendors. Here in routing u need to mention the info record etc. Lot of other setttings need to be done in this case.
However, the general settings are mentioned. Pls assign points if the above clarifies and let me know whether u hv sub contracting and external operation so that additional suggestion can be given further

Contents of new costing variant, valuation variant and costing sheet not getting transported

In our development client,I have created a new costing variant, a new valuation variant and a new costing sheet in separate transports.
When I release the transports to move into the Test client, the contents of the configuration are not getting transported at all.
I tried to do them again manually using Table view - Transport , but again, if I view the transports in SE10,they don't show the table contents, etc.
Any help on this will be highly appreciated.

Ajay,
Let me make sure I understand.
Create a new TR using SE01
Go to transaction OKKN (costing variant)
Select the costing variant and then choose Table view - transport
Provide the transport number
At what point to I say 'include in request'
If I try to use the menu option Edit-Transport-Include in request in the beginning itself, the 'Include in request' is greyed out.
This is where I'm stuck

Valuation price with user exit/BADI/Enhancement Spot (In valuation variant)

Hi all,
i am facing problem finding enhancement when creation of sales order of Valuation price with user exit/BADI/Enhancement Spot (In valuation variant)
For refferenece:
When going to t.code VA03, select one item and go to extras in the menu bar and select costing then you find some amounts calculation i.e valuation price automatically.
So when creation of sales order i am giving material and that material price automatically takes from material master and creating sales order.
My customer requirement is to get the valuation price of the input material from Z-table during the sales order cost estimate.
This Z-table contains the material code, plant , grade of the material.
Ex:
Material         Plant   Grade Price
A                1000    XYZ     25000
A                1000    PQR     35000
A                1000    BCD     45000
Suppose it depends on sales document type and which grade price i have to take.
So first of all i am unable to find enhancement where to change this code to get change the valuation price.
Does anybody have any idea , is there any user exit/BADI/enhancement for this.
So please help me in this issue.
Thanks & Regards,
lokeshgoud

pls allow me to post the questions

What are the major process to transfer the data from legacy to sap system.

What are the major process to transfer the data from legacy to sap system using BDC at Real Time only?

hi,
BATCH DATA COMMUNICATION
main methods are:
1. SESSION METHOD
2. CALL TRANSACTION
3. DIRECT INPUT
Advantages offered by BATCH INPUT method:
1. Can process large data volumes in batch.
2. Can be planned and submitted in the background.
3. No manual interaction is required when data is transferred.
4. Data integrity is maintained as whatever data is transferred to the table is through transaction. Hence batch input data is submitted to all the checks and validations.
To implement one of the supported data transfers, you must often write the program that exports the data from your non-SAP system. This program, known as a data transfer program must map the data from the external system into the data structure required by the SAP batch input program.
The batch input program must build all of the input to execute the SAP transaction.
Two main steps are required:
To build an internal table containing every screen and every field to be filled in during the execution of an SAP transaction.
To pass the table to SAP for processing.
Prerequisite for Data Transfer Program
Writing a Data Transfer Program involves following prerequisites:
Analyzing data from local file
Analyzing transaction
Analyzing transaction involves following steps:
The transaction code, if you do not already know it.
Which fields require input i.e., mandatory.
Which fields can you allow to default to standard values.
The names, types, and lengths of the fields that are used by a transaction.
Screen number and Name of module pool program behind a particular transaction.
To analyze a transaction::
Start the transaction by menu or by entering the transaction code in the command box.
(You can determine the transaction name by choosing System Status.)
Step through the transaction, entering the data will be required for processing your batch input data.
On each screen, note the program name and screen (dynpro) number.
(dynpro = dyn + pro. Dyn = screen, pro = number)
Display these by choosing System Status. The relevant fields are Program (dynpro) and Dynpro number. If pop-up windows occur during execution, you can get the program name and screen number by pressing F1 on any field or button on the screen.
The technical info pop-up shows not only the field information but also the program and screen.
For each field, check box, and radio button on each screen, press F1 (help) and then choose Technical Info.
Note the following information:
- The field name for batch input, which youll find in its own box.
- The length and data type of the field. You can display this information by double clicking on the Data Element field.
Find out the identification code for each function (button or menu) that you must execute to process the batch-input data (or to go to new screen).
Place the cursor on the button or menu entry while holding down the left mouse button. Then press F1.
In the pop-up window that follows, choose Technical info and note the code that is shown in the Function field.
You can also run any function that is assigned to a function key by way of the function key number. To display the list of available function keys, click on the right mouse button. Note the key number that is assigned to the functions you want to run.
Once you have program name, screen number, field name (screen field name), you can start writing.
DATA TRANSFER program.
Declaring internal table
First Integral Table similar to structure like local file.
Declaring internal table like BDCDATA
The data from internal table is not transferred directly to database table, it has to go through transaction. You need to pass data to particular screen and to particular screen-field. Data is passed to transaction in particular format, hence there is a need for batch input structure.
The batch input structure stores the data that is to be entered into SAP system and the actions that are necessary to process the data. The batch input structure is used by all of the batch input methods. You can use the same structure for all types of batch input, regardless of whether you are creating a session in the batch input queue or using CALL TRANSACTION.
This structure is BDCDATA, which can contain the batch input data for only a single run of a transaction. The typical processing loop in a program is as follows:
Create a BDCDATA structure
Write the structure out to a session or process it with CALL TRANSACTION USING; and then
Create a BDCDATA structure for the next transaction that is to be processed.
Within a BDCDATA structure, organize the data of screens in a transaction. Each screen that is processed in the course of a transaction must be identified with a BDCDATA record. This record uses the Program, Dynpro, and Dynbegin fields of the structure.
The screen identifier record is followed by a separate BDCDATA record for each value, to be entered into a field. These records use the FNAM and FVAL fields of the BDCDATA structure. Values to be entered in a field can be any of the following:
Data that is entered into screen fields.
Function codes that are entered into the command field. Such function codes execute functions in a transaction, such as Save or Enter.
The BDCDATA structure contains the following fields:
PROGRAM: Name of module pool program associated with the screen. Set this field only for the first record for the screen.
DYNPRO: Screen Number. Set this field only in the first record for the screen.
DYNBEGIN: Indicates the first record for the screen. Set this field to X, only for the first record for the screen. (Reset to (blank) for all other records.)
FNAM: Field Name. The FNAM field is not case-sensitive.
FVAL: Value for the field named in FNAM. The FVAL field is case-sensitive. Values assigned to this field are always padded on the right, if they are less than 132 characters. Values must be in character format.
Transferring data from local file to internal table
Data is uploaded to internal table by UPLOAD of WS_UPLOAD function.
Population of BDCDATA
For each record of internal table, you need to populate Internal table, which is similar to BDCDATA structure.
All these five initial steps are necessary for any type of BDC interface.
DATA TRANSFER program can call SESSION METHOD or CALL TRANSACTION. The initial steps for both the methods are same.
First step for both the methods is to upload the data to internal table. From Internal Table, the data is transferred to database table by two ways i.e., Session method and Call transaction.
SESSION METHOD
About Session method
In this method you transfer data from internal table to database table through sessions.
In this method, an ABAP/4 program reads the external data that is to be entered in the SAP System and stores the data in session. A session stores the actions that are required to enter your data using normal SAP transaction i.e., Data is transferred to session which in turn transfers data to database table.
Session is intermediate step between internal table and database table. Data along with its action is stored in session i.e., data for screen fields, to which screen it is passed, the program name behind it, and how the next screen is processed.
When the program has finished generating the session, you can run the session to execute the SAP transactions in it. You can either explicitly start and monitor a session or have the session run in the background processing system.
Unless session is processed, the data is not transferred to database table.
BDC_OPEN_GROUP
You create the session through program by BDC_OPEN_GROUP function.
Parameters to this function are:
User Name: User name
Group: Name of the session
Lock Date: The date on which you want to process the session.
Keep: This parameter is passed as X when you want to retain session after
processing it or to delete it after processing.
BDC_INSERT
This function creates the session & data is transferred to Session.
Parameters to this function are:
Tcode: Transaction Name
Dynprotab: BDC Data
BDC_CLOSE_GROUP
This function closes the BDC Group. No Parameters.
Some additional information for session processing
When the session is generated using the KEEP option within the BDC_OPEN_GROUP, the system always keeps the sessions in the queue, whether it has been processed successfully or not.
However, if the session is processed, you have to delete it manually. When session processing is completed successfully while KEEP option was not set, it will be removed automatically from the session queue. Log is not removed for that session.
If the batch-input session is terminated with errors, then it appears in the list of INCORRECT session and it can be processed again. To correct incorrect session, you can analyze the session. The Analysis function allows to determine which screen and value has produced the error. If you find small errors in data, you can correct them interactively, otherwise you need to modify batch input program, which has generated the session or many times even the data file.
CALL TRANSACTION
About CALL TRANSACTION
A technique similar to SESSION method, while batch input is a two-step procedure, Call Transaction does both steps online, one after the other. In this method, you call a transaction from your program by
Call transaction <tcode> using <BDCTAB>
Mode <A/N/E>
Update <S/A>
Messages into <MSGTAB>.
Parameter 1 is transaction code.
Parameter 2 is name of BDCTAB table.
Parameter 3 here you are specifying mode in which you execute transaction
A is all screen mode. All the screen of transaction are displayed.
N is no screen mode. No screen is displayed when you execute the transaction.
E is error screen. Only those screens are displayed wherein you have error record.
Parameter 4 here you are specifying update type by which database table is updated.
S is for Synchronous update in which if you change data of one table then all the related Tables gets updated. And sy-subrc is returned i.e., sy-subrc is returned for once and all.
A is for Asynchronous update. When you change data of one table, the sy-subrc is returned. And then updating of other affected tables takes place. So if system fails to update other tables, still sy-subrc returned is 0 (i.e., when first table gets updated).
Parameter 5 when you update database table, operation is either successful or unsuccessful or operation is successful with some warning. These messages are stored in internal table, which you specify along with MESSAGE statement. This internal table should be declared like BDCMSGCOLL, a structure available in ABAP/4. It contains the following fields:
1. Tcode: Transaction code
2. Dyname: Batch point module name
3. Dynumb: Batch input Dyn number
4. Msgtyp: Batch input message type (A/E/W/I/S)
5. Msgspra: Batch input Lang, id of message
6. Msgid: Message id
7. MsgvN: Message variables (N = 1 - 4)
For each entry, which is updated in database, table message is available in BDCMSGCOLL. As BDCMSGCOLL is structure, you need to declare a internal table which can contain multiple records (unlike structure).
Steps for CALL TRANSACTION method
1. Internal table for the data (structure similar to your local file)
2. BDCTAB like BDCDATA
3. UPLOAD or WS_UPLOAD function to upload the data from local file to itab. (Considering file is local file)
4. Loop at itab.
Populate BDCTAB table.
Call transaction <tcode> using <BDCTAB>
Mode <A/N/E>
Update <S/A>.
Refresh BDCTAB.
Endloop.
(To populate BDCTAB, You need to transfer each and every field)
The major differences between Session method and Call transaction are as follows:
SESSION METHOD CALL TRANSACTION
1. Data is not updated in database table unless Session is processed. Immediate updation in database table.
2. No sy-subrc is returned. Sy-subrc is returned.
3. Error log is created for error records. Errors need to be handled explicitly
4. Updation in database table is always synchronous Updation in database table can be synchronous Or Asynchronous.
Error Handling in CALL TRANSACTION
When Session Method updates the records in database table, error records are stored in the log file. In Call transaction there is no such log file available and error record is lost unless handled. Usually you need to give report of all the error records i.e., records which are not inserted or updated in the database table. This can be done by the following method:
Steps for the error handling in CALL TRANSACTION
1. Internal table for the data (structure similar to your local file)
2. BDCTAB like BDCDATA
3. Internal table BDCMSG like BDCMSGCOLL
4. Internal table similar to Ist internal table
(Third and fourth steps are for error handling)
5. UPLOAD or WS_UPLOAD function to upload the data from the local file to itab. (Considering file is local file)
6. Loop at itab.
Populate BDCTAB table.
Call transaction <tr.code> using <Bdctab>
Mode <A/N/E>
Update <S/A>
Messages <BDCMSG>.
Perform check.
Refresh BDCTAB.
Endloop.
7 Form check.
IF sy-subrc <> 0. (Call transaction returns the sy-subrc if updating is not successful).
Call function Format_message.
(This function is called to store the message given by system and to display it along with record)
Append itab2.
Display the record and message.
DIRECT INPUT
About Direct Input
In contrast to batch input, this technique does not create sessions, but stores the data directly. It does not simulate the online transaction. To enter the data into the corresponding database tables directly, the system calls a number of function modules that execute any necessary checks. In case of errors, the direct input technique provides a restart mechanism. However, to be able to activate the restart mechanism, direct input programs must be executed in the background only. Direct input checks the data thoroughly and then updates the database directly.
You can start a Direct Input program in two ways;
Start the program directly
This is the quickest way to see if the program works with your flat file. This option is possible with all direct input programs. If the program ends abnormally, you will not have any logs telling you what has or has not been posted. To minimize the chance of this happening, always use the check file option for the first run with your flat file. This allows you to detect format errors before transfer.
Starting the program via the DI administration transaction
This transaction restarts the processing, if the data transfer program aborts. Since DI document are immediately posted into the SAP D/B, the restart option prevents the duplicate document posting that occurs during a program restart (i.e., without adjusting your flat file).
Direct input is usually done for standard data like material master, FI accounting document, SD sales order and Classification for which SAP has provided standard programs.
First time you work with the Direct Input administration program, you will need to do some preparation before you can transfer data:
- Create variant
- Define job
- Start job
- Restart job
Common batch input errors
- The batch input BDCDATA structure tries to assign values to fields which do not exist in the current transaction screen.
- The screen in the BDCDATA structure does not match the right sequence, or an intermediate screen is missing.
- On exceptional occasions, the logic flow of batch input session does not exactly match that of manual online processing. Testing the sessions online can discover by this.
- The BDCDATA structure contains fields, which are longer than the actual definition.
- Authorization problems.
RECORDING A BATCH INPUT
A B recording allows you to record a R/3 transaction and generate a program that contains all screens and field information in the required BDC-DATA format.
You can either use SHDB transaction for recording or
SYSTEM ? SERVICES ? BATCH INPUT ? EDIT
And from here click recording.
Enter name for the recording.
(Dates are optional)
Click recording.
Enter transaction code.
Enter.
Click Save button.
You finally come to a screen where, you have all the information for each screen including BDC_OKCODE.
Click Get Transaction.
Return to BI.
Click overview.
Position the cursor on the just recorded entry and click generate program.
Enter program name.
Click enter
The program is generated for the particular transaction.
BACKGROUND PROCESSING
Need for Background processing
When a large volume of data is involved, usually all batch inputs are done in background.
The R/3 system includes functions that allow users to work non-interactively or offline. The background processing systems handle these functions.
Non-interactively means that instead of executing the ABAP/4 programs and waiting for an answer, user can submit those programs for execution at a more convenient planned time.
There are several reasons to submit programs for background execution.
The maximum time allowed for online execution should not exceed 300 seconds. User gets TIMEOUT error and an aborted transaction, if time for execution exceeds 300 seconds. To avoid these types of error, you can submit jobs for background processing.
You can use the system while your program is executing.
This does not mean that interactive or online work is not useful. Both type of processing have their own purposes. Online work is the most common one entering business data, displaying information, printing small reports, managing the system and so on. Background jobs are mainly used for the following tasks; to process large amount of data, to execute periodic jobs without human intervention, to run program at a more convenient, planned time other than during normal working hours i.e., Nights or weekends.
The transaction for background processing is SM36.
Or
Tools ? Administration ? Jobs ? Define jobs
Or
System ? services ? Jobs
Components of the background jobs
A job in Background processing is a series of steps that can be scheduled and step is a program for background processing.
Job name. Define the name of assigned to the job. It identifies the job. You can specify up to 32 characters for the name.
Job class. Indicates the type of background processing priority assigned to the job.
The job class determines the priority of a job. The background system admits three types of job classes: A B & C, which correspond to job priority.
Job steps. Parameters to be passed for this screen are as follows:
Program name.
Variant if it is report program
Start criteria for the job: Option available for this are as follows:
Immediate - allows you to start a job immediately.
Date/Time - allows you to start a job at a specific name.
After job - you can start a job after a particular job.
After event - allows you to start a job after a particular event.
At operation mode - allows you to start a job when the system switches to a particular operation mode.
Defining Background jobs
It is two step process: Firstly, you define the job and then release it.
When users define a job and save it, they are actually scheduling the report i.e., specifying the job components, the steps, the start time.
When users schedule program for background processing, they are instructing the system to execute an ABAP/4 report or an external program in the background. Scheduled jobs are not executed until they are released. When jobs are released, they are sent for execution to the background processing system at the specified start time. Both scheduling and releasing of jobs require authorizations.
HANDLING OF POP UP SCREEN IN BDC
Many times in transaction pop up screen appears and for this screen you dont pass any record but some indication to system telling it to proceed further. For example: The following screen
To handle such screen, system has provided a variable called BDC_CURSOR. You pass this variable to BDCDATA and process the screen.
Usually such screen appears in many transactions, in this case you are just passing information, that YES you want to save the information, that means YES should be clicked. So you are transferring this information to BDCDATA i.e., field name of YES which is usually SPOT_OPTION. Instead of BDC_OKCODE, you are passing BDC_CURSOR.
BDC_CURSOR is also used to place cursor on particular field.
A simple transaction where you are entering customer number on first screen and on next screen data is displayed for the particular customer number. Field, which we are changing here, are name and city. When you click on save, the changed record gets saved.
Prerequisite to write this BDC interface as indicated earlier is:
1. To find screen number
2. To find screen field names, type of the field and length of the field.
3. To find BDC_OKCODE for each screen
4. Create flat file.
generally Batch Input usually are used to transfer large amount of data. For example you are implementing a new SAP project, and of course you will need some data transfer from legacy system to SAP system.
CALL TRANSACTION is used especially for integration actions between two SAP systems or between different modules. Users sometimes wish to do something like that click a button or an item then SAP would inserts or changes data automatically. Here CALL TRANSACTION should be considered.
2. Transfer data for multiple transactions usually the Batch Input method is used.
check these sites for step by step process:
For BDC:
http://myweb.dal.ca/hchinni/sap/bdc_home.htm
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/home/bdc&
http://www.sap-img.com/abap/learning-bdc-programming.htm
http://www.sapdevelopment.co.uk/bdc/bdchome.htm
http://www.sap-img.com/abap/difference-between-batch-input-and-call-transaction-in-bdc.htm
http://help.sap.com/saphelp_47x200/helpdata/en/69/c250684ba111d189750000e8322d00/frameset.htm
http://www.sapbrain.com/TUTORIALS/TECHNICAL/BDC_tutorial.html
Check these link:
http://www.sap-img.com/abap/difference-between-batch-input-and-call-transaction-in-bdc.htm
http://www.sap-img.com/abap/question-about-bdc-program.htm
http://www.itcserver.com/blog/2006/06/30/batch-input-vs-call-transaction/
http://www.planetsap.com/bdc_main_page.htm
call Transaction or session method ?
null

Is it possible to run process chain from the certain process/point?

Hello
Is it possible to run process chain from the certain process?
How?
Thanks

Hello,
yes it possible! use the following steps.
1. Goto the process which you want the chain to start from.Goto display messages>> Chain tab. In the generated instance note the variant and instance.
2. Goto table RSPROCESSLOG and give variant and instance and get logid details.
3. t codese37>> run FM RSPROCESSFINISH.
4. give the deatils u have got in RSPROCESSLOG table here and say execute.
This will solve ur problem.
Hope this helps!
Reg
Deepmala

What is variant in ABAP Program Process Block in Process Chain?

I wrote an ABAP program:
REPORT ZTEST,
PARAMETERS: PROC(80) TYPE C.
I can test this PORGRAM from SE38, it shows me a pop-up screen for PROC and I can enter a value and execute.
Now I want to call this program ZTEST from a process chain. In Process Chain Selected a Process u201CABAP Programu201D. It asks me program name and Program variant, I entered Program Name as ZTEST and
Program variant as a character string HELLO.
When I execute Porcess Chain, ABAP Program errors saying that variant HELLO not found.
What is Program variant in ABAP Program Process in Process Chain?
Thanks,

Dont get confused here.
Variant name is not which you are pasing to the program.
You enter some values inside the variant and you specify the program to take the input from the variant.
Suppose you have to pass 10 parameters to a program.
user1 creates a variant " hello1" which contains his own selection for the 10 values
user2 creates another variant "hello2" which contain his own set of selecion values.
When we use this program in PC, you can use the variant user1 or user2 as per our requirement.
please check if you are giving variant as input or the proc value.
Hope this helps,
Sri....

No valuation variant found for valuation area

Dear Experts
When i m clearing or puting the LOt in quality through MB31 with 101 Movment for Production Order Following Error has occured
No valuation variant found for valuation area xxxx.
Rgds
Pankaj Agarwal

transaction - OPN2
for Valuation variant 007 see the details of material val tab page
if its defined properly
than go to
IMG--Production >SFC>Integration-->Define valuation of GR
assign 007 to ur valuation area that is plant code
hope this helsp

No valuation variant found for valuation area 4000

Dear Experts
When we are saving the production order we are getting the Following Error "No valuation variant found for valuation area 4000" i have check from my side the config for Valuation Varaint and Costing Variant is OK can any one please help me in this
we are running on EHP4 right now
Best Regards,

got the solution

Processing variant created by BRS process in SM35 ,i am facing error for Do

Hi,
When i am processing variant created by BRS process in SM35 ,i am facing error for Document search because it is searching through Ammount field ,after aswaining Document no in several placess it is not doing so
Thanks
CB

Check the log files in /Platformservices/workbench/workspace/logs folder. You will be able to find out the error

Table entry for Valuation variant for material prices

We want to define a valuation variant for costing run. In that we need to select the material price based on the plan price. We have provision of entering three plan prices in the Costing tab-2 in the material master. But we want to enter plan prices for more than three dates. For this, we propose to enter the dates and prices in a separate table and that table needs to be accessed in the valuation variant for material prices closest to the date of valuation. How we can go about this ?

Hi
When you create Valuation Variant, choose Strategy U i.e. Price from userexit
Then code the exit COPCP0005 with the help of ABAP consultant
The logic should be:
a. Refer the "costing date from" entered in Ck11N
b. refer the Z table... and pick the price relevant on that date
br, Ajay M

CK51N Valuation variant of the "ActivityTyes/Processes"

Similar Messages

Maybe you are looking for