Production version consistency check
Hi,
I am facing an issue in which i have created a BOM and a master recipe group. The production version is created and all the things are maintained properly so that consistency check shows green light i.e. everything is fine.
Then i delete the same material from recipe group and then do the consistency check then it turns to yellow since recipe group is missing.
But when i reassign the material to the recipe group and do the consistency check then also it remains in yellow and gives 2 line items in check result :-
one with message that task list exists.
and another with missing task list /material assisgnment .(in this the todate is the date on which i deleted the assignment)
My confusion is that after reassignment it should turn back to green but it is not.
Can you please help on this.
Thanks
Rohit
Hi Rohit,
Check Production Version Valid from date and also Date from when you have reassign that material in Master Recipe again.Both should be match.
Regards,
Dhaval
Similar Messages
-
Hi,
I have a BOM with 3 alternatives all with the same validity period.
The material master contains a production version which has been created for alternate 3.
When I create a production order shouldn't I get alternate 3 defaulting in????
I am currently getting alternate 1!!!!
My order type is set to 'Automatic Production Version' selection!!
Help!!!!
Thanks
StuartDear Stuart,
Please check what value you have given in the Selection method under BOM
Explosion/Dependent Requirements in MRP4 view of the material master.
Please check whether value 3(Selection only Production version) is maintained.
You can also use option 2 - Selection by Production version.
Check with this & revert to forums.
Regards
Mangal -
Hi ,
I am getting the below error on RTMT on CUCM 9.1 Version running on MCS 7835-I3-K9-CMD2 Error
At Sat May 24 03:12:40 IST 2014 on node , the following HardwareFailure events generated:
hwStringMatch : May 24 03:12:23 ASHISH-CM01 daemon 4 Director Agent:
LSIESG_AlertIndication 500605B005F63930 Consistency Check inconsistency logging disabled on VD 00/0 (too many inconsistencies) Sev: 3.
AppID : Cisco Syslog Agent
ClusterID :
NodeID : ASHISH-CM01
TimeStamp : Sat May 24 03:12:23 IST 2014
hwStringMatch : May 24 03:12:23 ASHISH-CM01 daemon 4 Director Agent:
LSIESG_StorageVolume_Modified 500605B005F63930 Consistency Check inconsistency logging disabled on VD 00/0 (too many inconsistencies) Sev: 3.
AppID : Cisco Syslog Agent
ClusterID :
NodeID : ASHISH-CM01
TimeStamp : Sat May 24 03:12:24 IST 2014
Does anybody has any idea on the same.
Your inputs would be appreciated ..
Regards,
Ashish BaglaHello,
Did you find the origins of the alerts? I have the same on 2 defferent servers about at the same time of the night a Saturday night too.
Looks like bug CSCts69041
Thansk,
Hervé Jacquemin -
How To Check Oracle Product Version (Ora 11g)
Hello!
I want to check my Oracle 11g product version (Standard or Enterprice, etc...).
I use this query:
select * from product_component_version
Result:
NLSRTL 11.2.0.1.0 Production
Oracle Database 11g 11.2.0.1.0 64bit Production
PL/SQL 11.2.0.1.0 Production
TNS for 64-bit Windows: 11.2.0.1.0 Production
How to check product version? (Standard or Enterprice, etc...)Try
SQL> select * from v$version;
BANNER
Oracle Database 10g Express Edition Release 10.2.0.1.0 - Product
PL/SQL Release 10.2.0.1.0 - Production
CORE 10.2.0.1.0 Production
TNS for 32-bit Windows: Version 10.2.0.1.0 - Production
NLSRTL Version 10.2.0.1.0 - Production
SQL>
Marcello -
Reg. Production Version Check Status
Dear All,
Is that necessary to check all created production version by clicking on CHECK button in production version details in MRP-4.
I have created production version, in C223 it is showing Green light in test status field, but in table MAPL field Check Status is blank.
Does it create any problem ?
Regards,
Archana.Hello Archana,
1. "is it necessary to always check status ?"
not necessary but whenever new creation/changes of master data,it must be done.
2. "MKAL status is blank" and "because in C223 it is indicating GREEN button in those production version records."
Both not possible together.If its showing green than MKAL status can not be blank.
3. "We have uploaded PV records, but not doing CHECKING procedure. I think, that is why status in MKAL is blank."
yes
4. "Does it create any problem in a future."
no,but better you check all scenario(standard/custom) of your company.Without performing check either in c223 or in material master,green light wont flash.Hope its clear.
Note:Whats the big deal if you do the check now?
Regards, -
Fileserver consistency checks failing 0x809909B0
I have a file server with approx. 1.7TB of files which became inconsistent on the 8<sup>th</sup> of November, and has been unable to complete a consistency check since then.
Consistency checks fail with the error:
The protection agent on <server> was temporarily unable to respond because it was in an unexpected state. (ID 60 Details: Internal error code: 0x809909B0)
I have removed and re-added the server, including deleting the protected data from DPM disk, and reinstalled the DPM agent on the file server, but I still receive the above error when consistency checking.
DPM is System Center 2012 R2 v4.2.1254.0 on Windows Server 2012 R2.
The file server is running Windows Server 2012 R2 also.
KB2919355 is installed on both systems.
I did have Dedup running on the file server, but have un-deduped the drive as part of troubleshooting this issue.
Other servers backed up by this DPM server are being backed up fine, including a HyperV cluster, 2 exchange servers and 2 sharepoint farms.
There are a large number of these errors in the DPMRA log around the time the job fails:
5288 4F48
11/28 22:49:56.601
29
radefaultsubtask.cpp(355)
[00000000013EE9D0] 50C1500F-0353-4D2A-8188-FC03612E2503
WARNING
Failed: Hr: = [0x809909b0] : CRADefaultSubTask: WorkitemID does not exist, {EB6F4726-E5C5-4958-B034-542518E5A931}
5288 4F48
11/28 22:49:56.601
05
defaultsubtask.cpp(546)
[00000000013EE9D0] 50C1500F-0353-4D2A-8188-FC03612E2503
WARNING
Failed: Hr: = [0x809909b0] : Encountered Failure: : lVal : CommandReceivedSpecific(pCommand, pOvl)
5288 4F48
11/28 22:49:56.601
05
defaultsubtask.cpp(751)
[00000000013EE9D0] 50C1500F-0353-4D2A-8188-FC03612E2503
WARNING
Failed: Hr: = [0x809909b0] : Encountered Failure: : lVal : CommandReceived(pAgentOvl)
5288 4F48
11/28 22:50:03.635
03
runtime.cpp(1376)
[00000000012F4850] 50C1500F-0353-4D2A-8188-FC03612E2503
FATAL Subtask failure, sending status response XML=[<?xml version="1.0"?>
5288 4F48
11/28 22:50:03.635
03
runtime.cpp(1376)
[00000000012F4850] 50C1500F-0353-4D2A-8188-FC03612E2503
FATAL <Status xmlns="http://schemas.microsoft.com/2003/dls/StatusMessages.xsd" StatusCode="-2137454160" Reason="Error" CommandID="RACancelAllSubTasks" CommandInstanceID="8a514c9b-6a62-42b4-a03b-0f938e3f20cc"
GuidWorkItem="eb6f4726-e5c5-4958-b034-542518e5a931" TETaskInstanceID="50c1500f-0353-4d2a-8188-fc03612e2503"><ErrorInfo xmlns="http://schemas.microsoft.com/2003/dls/GenericAgentStatus.xsd" ErrorCode="536872913"
DetailedCode="-2137454160" DetailedSource="2"><Parameter Name="AgentTargetServer" Value="DPM01.domain.com"/></ErrorInfo></Status>
5288 4F48
11/28 22:50:03.635
03
runtime.cpp(1376)
[00000000012F4850] 50C1500F-0353-4D2A-8188-FC03612E2503
FATAL ]
I have also tried the steps in this article with no change:
https://social.technet.microsoft.com/Forums/en-US/107bdce0-e13c-427a-9341-07d4b558f007/dpmra-crashing-after-update-to-dpm-2012-r2-ur2
Currently I have reduced the amount of shares being backed up to just ~400gb of data and I have it in a consistent state, but I need to get the remainder of the data backed up, and I can’t be in a situation where if it becomes inconsistent it can’t run a
successful consistency check again.Hi,
If you want to pursue this immediately, you can visit the following web site to open a support incident. The charge to your CC will not be processed until your case is resolved and closed, if it's a code defect in the DPM then we wave all charges.
http://support.microsoft.com/select/Default.aspx?target=assistance
In the Quick product finder, enter:System Center 2012 R2 - then select System Center 2012 R2 Data Protection Manager
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights. -
Error in making production version in material master..
the error is: to date is in the past.
Scenario: i am trying to maintain production version in the material master for finished material. this error is coming for each material. Pls help. points on the helpful answers..Dear,
Go to the MM02-MRP 4view clik on production version her you need to maintain the validity from From-To date as toadys date say11/11/2008 to 31/12/999 then double click on it then maintain the details like routing, bom and do the consistancy check if green light appear it means your PV is correct.
Regards,
R.Brahmankar -
About Tables of production versions
Hi
My planner needs to list all the materials which have a certain production,so,I need to know if there are any tables can have that connection.
Or could anyone tell me the table lists of production version related?
Thanks a lot!Dear Leo,
Check with
MKAL Production Versions of Material
to view the list of Production versions the T code is C223 &
C252 - Print List for Production version with consistency
Check.
Regards
Mangal -
What would be the easiest way to have the system show all Production Version's (C223) and their respective Route (CA01) relationship?
I want to make sure that all Production Version entries for ALL MATERIAL NUMBERS in the system coincide with the Routes that are turned on (status 4).
What method do you suggest I use to locate these?Dear Lucas,
Goto C223,enter the plant and press enter the system displays all the production versions available.
Now select all the entries and click on consistency check (test) button to identify whether the
production version is ok or not and then click on system in the top menu->list->save--->local file and
you can check the details.
otherwise you have to download the datas from the table MKAL or check whether C252 can help you.
Regards
Mangalraj.S -
LiveCache Consistency Check question, OM17
I have a general question about a LiveCache Consistency Check (transaction OM17). I know that it is a data inconsistency b/w the SAP APO database and SAP APO LiveCache. But what does that mean to a functional user? Can someone explain this in layman's terms?
In Layman terms, you can say that this checks the INCONSISTENCY between LiveCache and Database.
Here is a detailed documentation on each of the Object Types
Consistency Check for Setup Matrices
The consistency check for setup matrices contains:
· A check whether the setup matrices exist in liveCache
· A check whether the setup transitions exist in liveCache
· A field comparison between the setup transitions in the database and those in liveCache
When the setup matrices are corrected, the setup matrices in liveCache are completely generated from those in the database. Previously nonexistent setup matrices and setup transitions are newly created in liveCache. Superfluous setup transitions are deleted from liveCache. Setup transitions that differ at the field level are adjusted to match the database status.
Consistency Comparison for Block Basis Definitions
Use
When you set this indicator, checks are performed in liveCache and in the database on characteristic values for block basis definitions:
· The existence of block basis definitions is checked.
· The consistency of the characteristic values is checked.
After the checks you can call a correction function in the check results display. When correcting the error, the system deletes obsolete block basis definitions in liveCache. The system completes or corrects missing or inconsistent block basis definitions in liveCache.
Note
The check is performed independently of the planning version.
Consistency Check for Resources
The consistency check for resources contains:
· A check that the resource and corresponding time stream exist in liveCache
· An check that a resource's characteristic blocks exist in liveCache
· A field comparison between the database resource and the liveCache resource
When correcting the resources, the resources in liveCache are completely generated from the database resources. Previously nonexistent resources are created in liveCache.
Consistency check for downtimes caused by maintenance order
The consistency check for maintenance downtimes contains:
A check that the maintenance downtime has a reference to an existing maintenance order.
A check that the dates of maintenance downtime correspond to the exisiting maintenance order.
When correcting the maintenance downtime errors, downtimes without maintenance order are deleted and wrong dates of downtimes are corrected in relation to the maintenance order.
Consistency Check for Product Location Combinations
Use
If you set this indicator the system executes a consistency check for product location combinations. The consistency check for product location combinations includes:
· A check for the existence of a product location combination in the database and in liveCache
· A field comparison between product location combinations in the database and in liveCache
· The determination of obsolete entries for product location combinations in the database
· A check for the existence of characteristic value assignments for product location combinations in the database and in liveCache
· A field comparison of characteristic value assignments for product location combinations in the database and in liveCache
After the check you can call a correction function from the display of check results. For the correction, the system deletes obsolete product location combinations from the database and in liveCache. The system corrects inconsistent product location combinations and characteristic value assignments for product location combinations in liveCache.
Consistency Check for Stocks
Use
If you set this indicator the system executes a consistency check for stocks. The consistency check for stocks includes:
· A check for the existence of a stock in the database and in liveCache
· A field comparison between stocks in the database and in liveCache
· The determination of obsolete entries for stocks in the database
· A check for the existence of characteristic value assignments in the database and in liveCache
· A field comparison between characteristic value assignments for batch stocks in the database and in liveCache
After the check, you can call a correction function from the display of check results. For the correction, the system attempts to correct inconsistent stocks in the database and in liveCache. If a correction is not possible, the stocks are deleted in the database and in liveCache. The system corrects characteristic value assignments for batch stocks in liveCache.
After inconsistent stocks have been corrected, it may be necessary to start the delta report in order to reconcile SAP APO and SAP R/3.
Consistency Comparison of Configuration/CDP for Orders
Use
When you set this indicator, the system performs a consistency check with regard to configuration or CDP (characteristic value assignments/ requirements) for receipts/requirements belonging to orders:
· In the case of products with variant configuration and product variants, the system checks whether there is a referenced configuration in the database.
· In the case of products with CDP, the system checks whether CDP characteristics exist.
Note
In the area Restrictions, you can use the indicator CDP: Detailed Check to define a detailed check for CDP characteristics. If you set this indicator, the CDP data used for the orders is also compared with the product master.
· For products without configuration/CDP, the system checks whether invalid references to variant configuration or invalid CDP characteristics data exist.
After the check, you can call a correction function in the check results display. When executing the correction, the system tries to adjust inconsistent orders in liveCache.
After inconsistent orders have been corrected, you may need to start the delta report to compare the SAP R/3 system and SAP APO again.
Dependencies
The consistency check for configuration or CDP data is very time-consuming. You should therefore limit the comparison as far as possible to certain products or locations.
Consistency Check for Production Campaigns
If orders are assigned to production campaigns that do not exist in the database, this leads to inconsistent campaigns.
You can correct inconsistent production campaigns by removing all orders from them. That means that the campaign assignments are removed from the orders in liveCache.
Consistency Check for Operations
In the database table of /SAPAPO/OPR operations, there may exist operations that have no orders in liveCache, no orders for a simulation version, orders for deleted simulation versions, or no external operation number. These operations place an unnecessary load on the database table and can hinder system performance.
Consistency Check for Planning Matrices
As planning matrices are not master data, they are only located in liveCache. For each production version, there is a record in the database with information about matrices that must exist for this production version and whether the last matrix explosion was successful.
The consistency check for planning matrices checks:
· Whether the matrices associated with each record on the database exist in liveCache
· Whether the records associated with all the matrices in liveCache exist on the database
· Whether the last matrix explosion was successful.
If inconsistencies are discovered, they can be corrected. As corrections are made by recalculating the inconsistent matrices, the process can take a while and should only be done for large matrices (with many orders or many item variants) at times when it can be guaranteed not to hinder any other system processes.
Consistency Check for Simulation Versions
This is a check for whether simulation versions exist in liveCache.
Correction does not take place automatically. Simulation versions that still exist in the database but no longer exist in liveCache do not influence the running of the system. If necessary, they can be deleted using transaction /SAPAPO/CDPSS0.
Consistency Check for Product Allocations
The consistency check for product allocations checks the data for product allocation assignment from the database and compares this with the incoming orders quantity in Demand Planning. Surpluses or shortages are displayed and can be corrected.
The reconcile is only executed for product allocation groups with a direct connection to the product allocation group in the planning area if the connection is also fully defined.
There may be long runtimes during the consistency check due to the data structure. The following factors can hinder performance:
· Number of characteristics combinations
· Number of periods in a time series
· Number of sales orders that take product allocations from a time stream
Error in the reconcile
If it is not possible to reconcile the incoming orders quantity, the data records are issued again with a relevant error message. Check the following causes and attempt again.
Check:
· If the planning area to be checked is locked
· If the time streams are initialized (after liveCache has been initialized)
· If all characteristics combinations area available in the planning area
· The wildcard indicator for collective product allocation
· The settings for your planning area
Due Delivery Schedules/Confirmations Consistency Check
When a scheduling agreement release is received from a customer for sales and distribution scheduling agreement items, a due delivery schedule is created and stored in liveCache. As soon as a confirmation for a due delivery schedule containing at least one schedule line with a quantity larger than zero is generated, an object is also created for it in liveCache. The transaction data for sales and distribution scheduling agreement items contains, amongst other things, an entry with the key of the due delivery schedule object currently located in liveCache and an entry with the key of the confirmation that is currently valid in the database. During the check, the system checks whether liveCache objects exist for sales and distribution scheduling agreement items and whether the transaction data entries are correct.
The following individual checks are made for active sales and distribution scheduling agreement items:
· Is there an operative scheduling agreement release and/or forecast/planning delivery schedule in the database, but no associated liveCache object?
· Is there a confirmation in the database, but no associated liveCache object?
· Is there a due delivery schedule in liveCache, without at least one existing operative scheduling agreement release and/or forecast/planning delivery schedule?
· Is there a confirmation in liveCache, without an existing confirmation in the database?
· Is the key in the transaction data in the database that shows the current due delivery schedule in liveCache, also that of the actual liveCache object?
· Is there actually a confirmation in the database for the key in the transaction data that shows the currently valid confirmation in the database?
If a sales and distribution scheduling agreement item is inactive, there are not allowed to be any due delivery schedules or confirmations in liveCache. In this case, the following checks are made:
· Is there a due delivery schedule in liveCache for an inactive sales and distribution scheduling agreement item?
· Is there a confirmation in liveCache for an inactive sales and distribution scheduling agreement item?
Consistency Check for Production Backflushes
Partially confirmed orders cannot be deleted from liveCache. For each partially confirmed order of the database table, there must be a corresponding order in liveCache. If no order exists, there is a data inconsistency that can only be rectified by deleting the order from the database tables of the confirmation.
Entries for orders that have already been confirmed exist in the status matrix. The entry in an order's status matrix is deleted when the confirmed order is deleted by the /SAPAPO/PPC_ORD archiving report. Each status matrix entry for which database tables of the confirmation do not exist, present an inconsistency that can only be removed by deleting the status matrix entry.
Consistency Check for iPPE Objects
The iPPE object is not an iPPE master data structure. It is a data extract that is generated for each iPPE access object.
The consistency check for the object checks that it exists in liveCache and also determines its identity using the backup copy in the database. When correcting the object, the copy from the database is written to liveCache.
It is necessary to check the object if the following error message occurs: 'Error while calling COM routines via application program' (/sapapo/om 102) with return code 1601, 1602, or 1603. This does not apply to liveCache initialization.
Consistency Check for Procurement Scheduling Agreement Items
The following three objects represent procurement scheduling agreement items (scheduling agreement in short):
1. Scheduling agreement schedule lines
2. Release schedule lines
3. Confirmations
All these objects are located in liveCache. Release schedule lines and confirmations are also located in the database with a historical record. Depending on the process that was set up for the scheduling agreement, not all objects exist in liveCache or have historical records.
If goods movements exist for an object, there must always be at least one entry in liveCache. If all schedule lines are covered by goods receipts, at least one schedule line will exist in liveCache with the number '0000000000' and an open quantity of 0.
A liveCache crash, operator errors, and program errors can all cause inconsistencies. Below is a list of all the inconsistent statuses that have been identified and that can be removed:
1. The object is not in liveCache but goods receipts exist.
2. The number of input nodes and output nodes is different.
3. There are no input nodes at the order, but the material exists in the source location for the order.
4. The original quantity at the source of an order is different from that at the destination.
5. The accumulated quantities in liveCache are different from those in the database (the cumulative received quantity, for example).
6. The set process is compared with the status in liveCache.
7. A check is made to see whether the scheduling agreement is being planned in APO or in R/3 and whether the schedule lines have the appropriate specification.
If a schedule line inconsistency is identified, no more checks for inconsistencies are made, instead it moves on to the next schedule line.
Consistency Check for MSP Orders
Provides a list of maintenance and slot orders that
· Exist in the database but have no corresponding orders in the liveCache
· Exist in the liveCache, but have no corresponding orders in the database
Procedure
From within the list, you can either
· Correct the inconsistencies
If you choose to do this, the system deletes the selected orders from the database and/or liveCache.
You receive a message that the selected order(s) have been deleted.
· Leave the inconsistencies in the database and/or liveCache
Such inconsistencies place an unnecessary load on the database and/or liveCache. Moreover, those orders that exist in the liveCache, but have no corresponding orders in the database, influence the scheduling results of subsequent orders in the liveCache
Hope this helps
Regards
Kumar Ayyagari -
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
AmauryHi
Check user exit
QBCK0003 |Extended QM check for goods receipt
Regards
Sujit -
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 -
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_fieldl_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 -
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,
MehulHello 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 -
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?
tiaHi,
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
Maybe you are looking for
-
We have a Major Hospital/Clinic in Marshfield, Wisconsin yet very little if any coverage. I have complained numerious times only to be ignored. Why can't someone tell me why Verizion refuses to do anything? Sincerely, Kevin H << Personal information
-
Please anyone help me with my problem? Thx
-
I want to transfer my Macbook Pro info to a MacBook Air. 1-MacBook Air does not have Firewire 2-I do not have the ethernet adapter Is my only option to use WiFi? Isn't too slow and unreliable?
-
Installing Firefox with WIN 8.1
After installing Firefox I cannot open the programme as I get the pop up saying the http address is wrong. I have installed and used Firefox on this Toshiba laptop before with no problems.
-
This is the error i get, I have a 2 tb drive, (windows fresh install) and a 2 tb backup drive, completely formatted and empty. the 2nd drive was formatted full size, scroll over to see the 3 photos which show drives copied, it says only 33 gb was ne