Determine production version in cross plant failed

Hi folks:
I trying customizing and implementing a cross plant scenario:
*_Plant A01 - Production Plant_*
*+-- Material Mat001*
           +-- MRP 2 Procurement Type: E
           +-- MRP 4
                  1--- Selection Method: 3
                  2--- ProdVersions:
                           +--- Production version 001. Valid from / to 01.01.2000 / 31.12.9999
                           +--- Production version 002. Valid from / to 01.01.2000 / 31.12.9999
Plant A02 - Planning Plan
*+-- Material Mat001*
           +-- MRP 2 Procurement Type: E
           +-- MRP 2 Special Procurement: 80 ( to Plant A01 )
           +-- MRP 4
                  1--- Selection Method: 3
                  2--- ProdVersions:
                           +--- Production version 001. Valid from / to 01.01.2000 / 31.12.9999
                           +--- Production version 002. Valid from / to 01.01.2000 / 31.12.9999
Also, call transacction COR4 and change "order type parameters" to : "automatic selection of production version" for both plants.
But, i when run MPS ( MD41 / MD42 ) for material Mat001 in plant A02, production version is missing ( blank ).
Any ideas?
Someone has used badi MD_MODIFY_PRODVERS?
Thanks in advance,
César.

Hi All:
Well, I made a mistake. Do not update the selection method for the material in the planning plant.
Final Data |
Plant A01 - Production Plant
+-- Material Mat001
+-- MRP 2 Procurement Type: E
+-- MRP 4
1--- Selection Method: 3
2--- ProdVersions:
+--- Production version 001. Valid from / to 01.01.2000 / 31.12.9999
+--- Production version 002. Valid from / to 01.01.2000 / 31.12.9999
Plant A02 - Planning Plant
+-- Material Mat001
+-- MRP 2 Procurement Type: E
+-- MRP 2 Special Procurement: 80 ( to Plant A01 )
+-- MRP 4
1--- Selection Method: 3 <<<<<< WAS NOT UPDATE !!! >>>>>>>
I test badi MD_MODIFY_PRODVERS, but not necessary today.
Thanks ,
César.

Similar Messages

How can i get production version value(verid) for luck through bdc.

HI..
i have one requirement..that in c223 tcode while i luck the production version through BDC in my report program as i given bellow...i upload mat.no , plant, production version and 1(for luck)...
req:: i want while i given production version for particlular plant and material no...that production version should be luck....
so in standard tcode c223 how can i get value to compair it with my input production version value then i will close that...
program:::
report ZC2232
       no standard page heading line-size 255.
*include bdcrecx1.
Tables : mkal.
data : nodata value '/' .
data : CTUMODE type c value 'E'.
DATA : CUPDATE TYPE C VALUE 'L'.
DATA:   BDCDATA LIKE BDCDATA    OCCURS 0 WITH HEADER LINE.
      messages of call transaction
DATA:   MESSTAB LIKE BDCMSGCOLL OCCURS 0 WITH HEADER LINE.
data: begin of HEADER OCCURS 0,
data element: MATNR
        MATNR_001(018),
data element: WERKS_D
        WERKS_002(004),
data element: PLNNR
       PLNNR_003(008),
data element: CP_STTAG
        STTAG_003(010),
data element: ENTRY_ACT
       ENTRY_ACT_005(011),
data element: PLNAL
        PLNAL_004(001),
data element: FLG_SEL
       FLG_SEL_01_006(001),
data element: PLANTEXT
       STLAL_004(002),
       DATUV_005(010),
data element: WERKS_D
       WERKS_008(004),
data element: PLN_VERWE
       ktext_005(001),
data element: PLNST
        DELKZ_005(001),
data element: LOSGRVON
       LOSVN_011(017),
data element: LOSGRBIS
       LOSBS_012(017),
data element: PLNME
       PLNME_013(003),
data element: PLNME
       stlal_014(002),
end of HEADER.
data : begin of it_header occurs 0,
       matnr like marc-matnr,
       werks like marc-matnr,
       verid like mkal-verid,
       mksp like mkal-mksp,
       end of it_header.
data : exnum(40) type c,
       exnum1(40) type c,
       cnt type I,
       CN(2) TYPE C,
       c1 type c value '(',
       c2 type c value ')'.
start-of-selection.
parameters: p_file like rlgrap-filename.
at selection-screen on value-request for p_file.
call function 'F4_FILENAME'
EXPORTING
PROGRAM_NAME        = SYST-CPROG
DYNPRO_NUMBER       = SYST-DYNNR
FIELD_NAME          = ' '
importing
     file_name           = p_file.
start-of-selection.
call function 'WS_UPLOAD'
exporting
CODEPAGE                      = ' '
   filename                      = p_file
   filetype                      = 'DAT'
HEADLEN                       = ' '
LINE_EXIT                     = ' '
TRUNCLEN                      = ' '
USER_FORM                     = ' '
USER_PROG                     = ' '
DAT_D_FORMAT                  = ' '
IMPORTING
FILELENGTH                    =
tables
    data_tab                      = it_header
EXCEPTIONS
CONVERSION_ERROR              = 1
FILE_OPEN_ERROR               = 2
FILE_READ_ERROR               = 3
INVALID_TYPE                  = 4
NO_BATCH                      = 5
UNKNOWN_ERROR                 = 6
INVALID_TABLE_WIDTH           = 7
GUI_REFUSE_FILETRANSFER       = 8
CUSTOMER_ERROR                = 9
NO_AUTHORITY                  = 10
OTHERS                        = 11
if sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
endif.
DELETE it_header WHERE MATNR IS INITIAL.
LOOP AT it_header.
*start-of-selection.
*perform open_group.
perform bdc_dynpro      using 'SAPLCMFV' '1000'.
perform bdc_field       using 'BDC_OKCODE'
                              '=ENTE'.
perform bdc_field       using 'BDC_CURSOR'
                              'MKAL-WERKS'.
perform bdc_field       using 'MKAL-WERKS'
                              it_header-werks.
perform bdc_field       using 'MKAL-MATNR'
                               it_header-matnr.
perform bdc_dynpro      using 'SAPLCMFV' '1000'.
perform bdc_field       using 'BDC_OKCODE'
                              '=PICK'.
perform bdc_field       using 'MKAL-WERKS'
                             it_header-werks.
perform bdc_field       using 'MKAL-MATNR'
                            it_header-matnr.
*>>>>>>>>>>>>>>>>>>>>here what logic can i write****
clear cnt.
do 15 times.
cnt = cnt + 1 .
CN = CNT.
exnum = 'MKAL_EXPAND-VERID'.
concatenate exnum c1 cn c2 into exnum1.
*perform bdc_field       using 'BDC_CURSOR'
                               exnum1.
GET PARAMETER ID 'VER' FIELD EXNUM1.
CALL TRANSACTION 'C223' AND SKIP FIRST SCREEN.
if ( it_header-verid = EXNUM1 ).
exit.
endif.
enddo.
****************************************************end***>>>>>>>>
perform bdc_field       using 'BDC_CURSOR'
                              exnum1.
perform bdc_dynpro      using 'SAPLCMFV' '2000'.
perform bdc_field       using 'BDC_CURSOR'
                              'MKAL_EXPAND-PLNTY'.
perform bdc_field       using 'BDC_OKCODE'
                              '=PRFG'.
perform bdc_dynpro      using 'SAPMSSY0' '0120'.
perform bdc_field       using 'BDC_OKCODE'
                              '=RW'.
perform bdc_dynpro      using 'SAPLCMFV' '2000'.
perform bdc_field       using 'BDC_OKCODE'
                              '/ECANC'.
perform bdc_field       using 'BDC_CURSOR'
                              'MKAL_EXPAND-VERID'.
perform bdc_dynpro      using 'SAPLCMFV' '1000'.
perform bdc_field       using 'BDC_OKCODE'
                              '=SAVE'.
perform bdc_field       using 'BDC_CURSOR'
                              'MKAL-WERKS'.
perform bdc_field       using 'MKAL-WERKS'
                              it_header-werks.
perform bdc_field       using 'MKAL-MATNR'
                              it_header-matnr.
perform bdc_dynpro      using 'SAPLCMFV' '1000'.
perform bdc_field       using 'BDC_OKCODE'
                              '/EBACK'.
perform bdc_transaction using 'C223'.
endloop.
*perform close_group.
*&      Form bdc_dynpro
      text
     -->P_0161   text
     -->P_0162   text
form bdc_dynpro USING PROGRAM DYNPRO.
CLEAR BDCDATA.
BDCDATA-PROGRAM = PROGRAM.
BDCDATA-DYNPRO   = DYNPRO.
BDCDATA-DYNBEGIN = 'X'.
APPEND BDCDATA.
endform.                    " bdc_dynpro
*&      Form bdc_transaction
      text
     -->P_0351   text
form bdc_transaction USING TCODE.
call transaction 'C223' using bdcdata
                         mode    CTUMODE
                         update CUPDATE
                         messages into messtab.
if sy-subrc <> 0.
message e000(zmm01) with
'Check your input data'.
endif.
endform.                    " bdc_transaction
*&      Form bdc_field
      text
     -->P_0346   text
     -->P_0347   text
form bdc_field USING FNAM FVAL.
if fval <> nodata.
    CLEAR BDCDATA.
    BDCDATA-FNAM = FNAM.
    BDCDATA-FVAL = FVAL.
    APPEND BDCDATA.
    endif.
    endform.                    " bdc_field

l_nl := dbms_xslprocessor.selectNodes(l_n, '/TaxInvoice/TaxInvoiceDocument');try to change as follow
l_nl := dbms_xslprocessor.selectnodes(l_n,'/TaxInvoice/TaxInvoiceDocument','xmlns="urn:kr:or:kec:standard:Tax:ReusableAggregateBusinessInformation:1:0"');Edited by: AlexAnd on Aug 17, 2011 12:36 AM

Receiver Determination when multiple Product Versions / identical namespace

Hi,
How would the receiver determination be done when we have multiple product versions with identical namespaces and interface names ?
During development, when we do a release transfer to another product version, the namespaces and interface names remain same as the current objects.
How would XI resolve the correct interface in this case ?
thanks,
Manish

The XI does not care about the application systems. When a message is received by the application, it knows, what to do with the messages.
The receiver could be an RFC call, an IDOC, an Abap Proxy, here the correlation between interface and Abap code is unique.
The receiver could be a File, or JMS adapter, here the correlation between interface and communication channel is unique as well.
You might reuse IDOCs or RFCs or in rare situations other interfaces in different software components and install them for the same application system. But you can only generate proxies from one interface.
Regards
Stefan

How to realize cross-plant ATP check in 46c when creating SO

Hi all
For cross-plant ATP check is not available in 46c when creating SO, is there other way to realize it? Can it be realized through user-exit or enhancement or development?
Is there anyone can help me?
Best regards
Egg

see these user exits for VA01. Second one can be used for ATP check...
check below enhancements in SMOD Tcode .
SDAPO001 Activating Sourcing Subitem Quantity Propagation
SDTRM001 Reschedule schedule lines without a new ATP check
V45A0002 Predefine sold-to party in sales document
V45A0003 Collector for customer function modulpool MV45A
V45A0004 Copy packing proposal
V45E0001 Update the purchase order from the sales order
V45E0002 Data transfer in procurement elements (PRreq., assembly)
V45L0001 SD component supplier processing (customer enhancements)
V45P0001 SD customer function for cross-company code sales
V45S0001 Update sales document from configuration
V45S0003 MRP-relevance for incomplete configuration
V45S0004 Effectivity type in sales order
V45W0001 SD Service Management: Forward Contract Data to Item
V46H0001 SD Customer functions for resource-related billing
V60F0001 SD Billing plan (customer enhancement) diff. to billing plan
V45A0001 Determine alternative materials for product selection
Regards,
Madan gopal Sharma..
REWARD POINTS

Cross Plant Planning- MRP activation indicator turned after the creation of Material code

Dear Experts,
Working on Cross plant planning, where 1001 Production plant will stock transfer material to 8 different plants.
Right now, only 10001 plant had MRP and planning file entry ticked in customizing OMDU.
The other 8 plants have Materials codes created and MRP views extended but no MRP activation is ticked.
Now, to have Cross plant planning MRP set, I have done necessary configurations, Scope of Planning, Special Procurement 40, and parallel processing is configured. All master datas are set properly. Tested few scenarios in IDES, working fine.
If my understanding is clear, than I thin I need to run MDAB, activation of planning file and MDRE, Planning file Consistency Check, because MRP will run in background?
Is this correct or something more needs to be done ?? Please suggest
Please also tell what is the use of MDRE t code.
Best regards
Shailesh

Hello Shailesh
MDAB (RMMDVM20) is at plant level, you need to create different variants as per your plants
Create a variant for the new plants and then schedule a job for these variants.
Check customizing transaction OMDU -> set up planning file
entry and consistency check of planning file entries.
Best Regards,
R.Brahmankar

There is already a transaction for the systems of this product version(MOPZ)

Hello All,
I am trying to configure maintenance optimizer in Solution Manager 7.0
on Windows 2003 server and SQL 2005 server.
I am configuring this for SAP CRM 2007 server.
Created the server, database and system in SMSY
Created Logical Component in TA code SMSY
SM59 connection for SAP-OSS is OK.
S-User is assigned to a User.
Created a solution using TA code solution_manager.
Defined the product version for the solution created in the TA code
solution_manager.
When creating a Maintenance Optimizer transaction, I select the
product version and its logical component in the Plan Maintenance
(Phase) and click on Continue to go to Select Files Phase, I get below
warning:
Information Procedure 8000000130 Saved
Warning: Status was reset by system
Warning: There is already a transaction for the systems of this
product version
I cannot get pass this phase.
I have deleted and recreated the solution, carried out the same
activity again but its giving the same Warning
Warning: Status was reset by system
Warning: There is already a transaction for the systems of this
product version
Any help will be appreciated???
Regards,
Satish.

Hello Ragu,
Thanks for your response.
As of now, we do not have ChaRM in place. Secondly, we use a single customer number.
I would like to let you know that in our landscape we have two CRM server, one ECC sever, one SOLMAN7.0 server.
I tried to configure MOPZ for CRM, ECC, SOLMAN server to download the respective STACKS.
I was successful in configuring CRM and SOLMAN.
But when I tried to configure in ECC, it failed due to RFC erros.
So I deleted the transaction for the ECC system and deleted the system itself in Solution Manager.
Reconfigured the Systems in "SMSY", RFC connections are correctly defined to configure MOPZ between SOLMAN7.0 and ECC6.0.
When I start configuring the MOPZ, I cannot get pass the first phase and this is when I get an error: There is already a transaction for the systems of this product version.
Please let me know if you need further information.
Regards,
Satish.

How to determine the version of Identity Manager 9.1 with the build number

Friends,
I have a query this compilation of Identity Manager that show below that corresponds Identity Manager version: 9.1.0.1, 9.1.0.2 or 9.1.0.3
As I can determine this information.
Diagnostic Dashboard
System Information:
Application Server: JBoss
Oracle Identity Manager Installation:
Product Version: *9.1.0.1860.16*
Build Number: 1860.16
Host: serveroimoooo53
Location: C: / IOM / xellerate
Thanks

That is version 9.1.0.1 base installation.
You can find the information by logging into metalink (http://metalink.oracle.com) and searching. I used the Build Number to return results.
-Kevin

Costing variant and production version

We have two costing variants "C" (used to create current cost estimates) and "F" (Used to create Future cost estimate). All of the production versions in the system have a validity date of 9999. Is there a way to tell the system to use one production version when costing using Variant C and another version when costing is done using variant F.
Or if that is not possibel than how do we use one production version in 2011 while recosting current standards and another production version in 2012. (Remember the production version that we are using currently in 2011 has a validity date of 9999)
Regards

Hi
In your Costing Variant - You have a tab callled "Qty Structure Control".... Here you can specify BOM Determination and Routing Selection id.... i.e. If the BOM / Routing attached to the prod version can be assigned a specific BOM Determination Class and Routing Selection id, it can work
OR ELSE
While doing CK11N, you can manually specify the Prod Version in the "Qty Struct" Tab..... Create an LSMW for CK11N and you can do a mass costing like CK40N.... CK40N does not have this option of specifying Prod Version
I would prefer 2nd option
Br, Ajay M

Change Production version during creation of Process Order COR1

Hi,
Scenario:
Based on the entered Material, Plant and Order type system need to trigger a popup asking the user to select the Production Version. This should happen before clicking on SAVE button, so that all the values will be populated correctly based on the changed VERID.
I did not find a user exit that enables to change the Production Version (VERID) value. So I thought of displaying the popup in the user exit EXIT_SAPLCOZF_003 which will be triggered before initial screen appears, export the selected value and pass it to a User Exit or BADI where VERID can be changed. But cannot find a user exit to do it.
Please help me find a User Exit or BADI to change the Production Version during creation of Process Order using COR1 transaction before clicking on SAVE button.
Thanks,
Manoj.

Hi Manoj,
So - almost four years later - I saw your post and I saw myself in the very same situation as you did...
I found a solution for those who wants to change the production version of the production order from the sales order creation: create an enhancement in the function module 'MD_VERSION_SELECTION' and you are good to go.

How to add production Version field in COOIS to selection options?

Dear Experts,
Need your suggestion for below issue raised by client.
1) As per client, he was running COOIS with the selection option of a production version. But currently he is not able to see this selection while executing a COOIS t-code.-----> Kindly guide me on its possibilities & necesary checks.
2) If I want to correct it & want to add Production Version field in COOIS report what steps I should take?
Need all your valuable guidence to resolve above issue.
Thanks & Regards,
Mehul

Hello Vivek,
Really thanks for your mail. Please see below comments-
1) I checked the transaction COOIS & also told user to select Production Version after executing the report by giving Plant code & dates. But user asking for this field before execution.
As per your suggestion I checked in Header level of first screen but its not showing me also.
2) I am using ECC6.0 version
3) One finding from my side- This is I am checking only selecting Production Orders. But when I am selecting only Planned order then Production version can be seen in first screen under Repetitive Mfg. section.
so kindly tell me why this not showing when Production order selected?
Thanks in Advance for your help.
Regards,
Mehul

Scrap Valuation Report by Production Version.

Dear All.,
Need the suggetions & help to me on the below mentioned scenario.
Scenario
        My Client into MFG sector. What ever the material produced by my client is have different production versions. Moreover, we have multiple plant in which few are Repetitive Mfg with Product Cost Collectors & few are Discreat MFG Process.
       As we will get the scrap values after each confirmation by Qty & Value.
       So, the user is asking the report on SCRAP for all the stages of Product (Structure in CS11) by Production Version Wise.
Current Availability
          We have standard Reports like KKFB, KOBB, KRM, S_ALR_87012151 - 52, S_ALR_87013148-49 & even in the cost estimate (CK11N) which are giving the Scrap details by Quatity & Value as well. But those value are limited to only one Prodcution Version.
Requirement
          I want the details on HOW CAN WE GET the SCRAP detailed analysis at Product Hierarchy with reference to all Production Versions.
Pls Give some inputs on this.
Thanks in Advance.....
TRS....

Hi Talluri,
Thanks for your reply.
could you please forward documents to anusha.r3 at gmail
i will assign points.
I have some questions also..please help me.
1. What is the flow in MTO process? Could you please explain me step by step process?
2. Do we run standard cost estimate for MTO costing?
3. What are step involved in month -end process like WIP or RA calculation, Variance and Settlement for MTO?.
4. For MTS process we have material master setup with standard price(S) indicator for materials, what about materials master in MTO process?
5. For RA calculation in project systems we plan cost and revenue on WBS and how and where we plan cost and revenue in MTO process?
6. What is the difference between valuated stock and non valuated stock?
Thanks,
Anusha
Thanks

How to identify Production Version in wwv_usr_menus

In the Portal application menu wizard, you can 'Edit as New' from the manage menu UI. This creates a new menu version and row for menu_id in wwv_usr_menus$. You can also select which version (from n number of versions) should be current. Question is :
How do you determine in custom application sql which version is current in wwv_usr_menus$, no 'Active' column, or iscurrent column exists. I've checked following:
1. FK Constraint to wwv_usr_menus$ table = 0
2. Trigger on table for seeding surrogate key only
3. No menu API in PDK documentation, i.e. boolean = iscurrentmenu(menu_id, version);
4. Update_dt column only updated when version is modified, not re-selected as current active version in Menu Manage UI.
5. max(version) returns the last version created, not the current active (production) version.
Code for rendering menu manage page is wrapped, I think the logic is there?
Must be another table (not RI linked) that has current Menu version information.
SO!!!!
64,000 question is 'How do you know (programmatically) which row in portal.wwv_usr_menus$ is current version, or when you click 'Make version 2 as Production Version', what table is updated in portal schema?
tia

Hi,
I think I have already answered this one. You can get the curent version either from wwv_usr_menus$ or wwv_modules$
select version from wwv_modules$
where id = <module_id>
and status = 'PRODUCTION'
This gives the version of the current production version.
Thanks
Sharmila

How to determine the version of xmlparserv2.jar?

Hi,
Is there any way I can determine the version of an
xmlparserv2.jar file?
I am using XML Parser V2 (xmlparserv2.jar) with the following
file size: 1,086,234 bytes.
This was supplied with JDeveloper 3.1 but I have no idea what
version is it? Any help on this will be appreciated.
TIA,
-Piyush

the class oraxml does not exist in this version of the jar!
however i do see an entry like: xmlparser_2.0.2.6_production
when i open the jar file in winzip!
i have cross verfied with other xmlparserv2 files (diff file
sizes) and this seems to be it.
thanks for the suggestion.
regards,
-Piyush

Production version report

Hi Gurus,
is there a report that can give information about production versions. The fields at a minimum that i'm looking for are production version, material, text, alternate BOM, product line, Group, plant, valid from, lock, task list type, valid to, Bom usage
Thanks
Anusha

Anusha,
To my knowlede you cannot export it to Spread sheet from C223. If you need to download, then you can take it by table browser transaction SE16 from table MKAL.
1. Execute transaction SE16.
2. Input table as MKAL. Input the selection critera and also set the output fields and then execute.
3. You would be able to export this output to Spread sheet.
Regards,
Prasobh

REM Product cost collectors and Production version

Hi All,
Can some one pls let me know
What are the product cost collectors in REM and how to create the product cost collectors ?
What is the production version and the difference between production version and controlling version?
Thanks & Regards,
Bujji

Dear Bujji,
A product cost collector is a cost object in Product Cost by Period that collects the periodic actual costs incurred in the production of a material. It can be created in txn KKF6N.
[Product Cosr Collector|http://help.sap.com/saphelp_47x200/helpdata/EN/08/77ba810a1611d3a6b900104b55d538/frameset.htm]
[Product Cost Collectors: Collective Entry for Repetitive Manufacturing |http://help.sap.com/saphelp_47x200/helpdata/EN/08/77ba810a1611d3a6b900104b55d538/frameset.htm]
A production version determines the various production techniques that can be used to produce a material. It defines the following information:
Alternative BOM for a BOM explosion
Task list type, task list group, and group counter for assignment to task lists
Lot-size restrictions and period of validity
A material can have one or more production versions.
It can be defined in the Material Master (txn MM02) in one of the following views:
MRP 4
Work Scheduling
Costing 1
The costing version is a different issue. It is a costing parameter and is used to save several cost estimates for the same material, with the same costing variant and the same costing date (e.g. in oder to cost the material several times with minor changes without creating new costing variants).
BR,
Antje

Determine production version in cross plant failed

Similar Messages

Maybe you are looking for