Wwv_usr_menus$ Production version

How do you tell which version in the wwv_usr_menus$ table is the production version?
Version column contains the version number, not whether it is production!
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

Similar Messages

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 get production version in your contract?

hi all,
I have already maintain multiple production versions for one product, but how can I let it appear in the contract item?
thanks

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

Creation of inspection lot 04 depending on production version

Hi Experts,
could you tell me if it is possible to create a Good Receipt inspection (lot origin 04) depending on the production version used ?
My material has 2 production versions:
0001 - production with process order
0002 - production with repetitve manufacturing
When I do a GR on process order, I do not want to create an inspection lot 04.
When I do a GR on product cost collector, I want to create an inspection lot 04.
As I have entered inspection types in material master data, I do not know how to do the distinction ?
Thanks in advance for your help
Best regards
Amaury

Hi
Check user exit
QBCK0003 |Extended QM check for goods receipt
Regards
Sujit

ISSUE:regarding production version tab of MRP4 of data transfer using BD10

Hi all,
This is regarding production version tab of MRP4 of data transfer using ALE idoc (BD10).
When i transfer the data using BD10 the production version is received at receiving end through segment
but not created in MRP4 view tab.An error is coming as-
"You wanted to maintain the master record of the material AB_06.04.09(2). However, it is already being processed by the user EBGABAP and is therefore locked."
I logged in as-EBGABAP
Please help me resolve the issue.
Thanks
Edited by: sanu debu on May 6, 2009 11:08 AM
Edited by: sanu debu on May 6, 2009 11:09 AM
Edited by: sanu debu on May 6, 2009 11:11 AM

>
sanu debu wrote:
> Hi,
> I have to upload production version tab data of MRP4 view(MM01).Please suggest a function moduleor bapi for the same.
>
> Thanks.
>
> Edited by: sanu debu on May 6, 2009 3:24 PM
BAPI_MATERIAL_SAVEDATA can be used, populate the respective fields in input parameter PLANTDATA

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.

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

QC Activity based on Material Production Version

Hi,
Normally, we perform QC activity based on Material Code, i.e. in Material Master we maintain inspection type in QM View for material which needs QC activation during Good Receipt from Production
Is it possible to perform QC Activity based on Production Version of a material i.e.
For Example
Product A having 2 Production Versions
IF Product A with Production Version 1 then No QC required during goods receipt from production
IF Product A with Production Version 2 then QC required during goods receipt from production
So please tell me what feasible solution possible from your side
With Regards,
Kunal Sheth

Dear Sap User,
Production version is nothing just a combination of Master recipe/Routing and BOM used for particular production or process.
If you are having so many production version then you have to choose which you want to choose but if you are having a single production version then it will be chosen automatically.
Do it once and revert in case of any query.
Rgrds,
Dheeraj Rawal
Edited by: Dheeraj89 on Feb 9, 2012 6:13 AM

Production Version of Co Product

Hi,
I have got one main product and one co product. Main product has got many Production Version based on lot size. When I do costing for the main product ,it picks the right PV based on the lot size. But in case of co product costing it picks the first PV of main product only irrespective of lot size. Why ?
Shahnawaz

>
Shahnawaz Farooqui wrote:
> Hi ,
> I am not maintaining separate BOM for co product . As mentioned in my question it is when I am doing the costing for Co product it is picking the wrong PV of main Product.
>
> Shahnawaz
Shahnawaz,
Why you are doing seperate costing for CO-Product, when you do costing for main product it should do cost roll-up for the co-product also. Please check
Regards,
Prasobh

Different fix lot size depending on the production version

Hi all,
I have the next scenario:
2 production versions. 2 different fix lot size por each. So:
Prod Version 1 - Fix lot size 200
Prod Version 2 - Fix lot size 300
I created the Quota Arrangement just to make SAP to take my favourite version. And trought the quota, I can define the lot size for each version. BUT.
If I change the version in the order or in the planned order, the quantity don't change.
So: How can I manage 2 different fix lot size for 2 different product versions? If I change the version once the order is created, how can I do the system change de quantity to the right one?
Thanks in advante
<< Please do not offer points >>
Edited by: Rob Burbank on Oct 1, 2010 2:53 PM

I have n't tried this scenario,
This is my Idea
Create a two production version
for ex: lot size 100 to 1000, set the rounding profile qty as 1000
for lot size 1001 to 99999, set the lot rounding profile value to 5000
BY this way u can get the two lot based on the rounding profie
Expert; please correct if i am wrong
Edited by: Sundaresan . E. V on Oct 1, 2010 4:12 PM

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.

Transfer of Production Version

Hi Gurus,
i am trying to transfer the Production Versions of a Material to an other System via IDoc. I am using BD10 for transfering.. The relevant Segment E1MKALM in MATMAS05 is filled with all data from the source. But in the Target Systen tge Production Version is not added (Material exists already in Target system, only addition is needed).
what am i am doing wrong? The Segment E1MKALM is directly for Production Version, but why this is not used in the target system? There are no errors in BD87 when i process the IDoc.
any Ideas?
Best Regards
Udo

no answered but i dont want this question to hang in ....

BAPI/Function module for production version tab data of MRP4 view(MM01).

Hi,
I have to upload production version tab data of MRP4 view(MM01).Please suggest a function moduleor bapi for the same.
Thanks.
Edited by: sanu debu on May 6, 2009 3:24 PM

>
sanu debu wrote:
> Hi,
> I have to upload production version tab data of MRP4 view(MM01).Please suggest a function moduleor bapi for the same.
>
> Thanks.
>
> Edited by: sanu debu on May 6, 2009 3:24 PM
BAPI_MATERIAL_SAVEDATA can be used, populate the respective fields in input parameter PLANTDATA

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

Production Version in Material Master

Hi,
I am having problems with this.
I need to either change date on a production version or
delete the product version.
I have tried using a batch input sequence from my program both for changing the date
and for deleting the production version and this all works well.
Now this isn't good enough since there can be multiple production versions on a material
and I don't know which line to change or delete in the batch run.
Is there a good FM or BAPI to handle this?
I don't want to change the MKAL table directly since there is a history table
connected to this also (MKAL_AEND).
What is the best approach?
Rgds,
/Fredrik.

How can I use this to achieve what I want to do, either
change the production version date or delete the production version?
I have tried C223, but this is not good enough, nor is batch run in MM02.
I can have multiple production versions and can not pick the correct line
in batch run to change or delete.

Wwv_usr_menus$ Production version

Similar Messages

Maybe you are looking for