OPM Financials Trouble Shooting Guide

9/25/13
Document 1213193.1
OPM Financials (GMF) Troubleshooting Guide (Doc ID 1213193.1)

Modified: Oct 11, 2012 Type: FAQ Status: PUBLISHED Priority: 1
In this Document Purpose Questions and Answers References
APPLIES TO:
Oracle Process Manufacturing Financials - Version 11.5.10 to 12.1.3 [Release 11.5 to 12.1] Information in this document applies to any platform. All opm financials forms, reports, concurrent requests for release 11i and 12
PURPOSE
This document provides basic to advanced trouble shooting information which can be used by Customers, Support and Development.
QUESTIONS AND ANSWERS

This note provides troubleshooting information for OPM Financials Module (GMF). It covers the following topics. 1. How to enable Debug Log mode for Concurrent Programs 2. Find File versions, Profile values and Patches Applied 3. Find Log File and Error messages for important processes Cost Rollup Actual Cost Lot Cost Cost Update Test Subledger Update Final Subledger Update Detailed Subledger Report OPM Accounting Pre- Preprocessor Create Accounting 4. 5. 6. 7. 8. Enable Forms Trace Enable Reports/Concurrent Request Trace Important Tables in 11i and R12 Important SQL queries and filtering transaction related issues Relayering in Actual Costing
For any OPM Financials issue Oracle Support request that you provide the file versions, log file with debug mode, error messages, screen shots and steps followed. 1.How to enable Debug Log mode
https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=rhj7sao4j_57&id=1213193.1 1/20
9/25/13
Document 1213193.1
(Enabling Debug mode in OPM Financials) These steps are same in 11i and R12 Profile name : GMF Debug Log Level Valid values : Null, 0,1,2 & 3. Set this profile value to 3 to enable the Debug mode and set it to Null in order to disable debug mode. This profile can be set from Menu -> Edit->Preferences ->Profiles->Personal Profile Values (Screen) . Query for profile name %GMF%Debug%. (The long name of the Profile may vary - it is frequently set up as "GMF: Concurrent Debug Flag"). If profile value can not be seen from menu check by logging with the responsibility of system administrator. Otherwise contact your system administrator. If this profile does not exist or if this is a new instance then this profile has to be created. Define new profile GMF_CONC_DEBUG as below: Responsibility: Application Developer. In case you do not have this responsibility ask your dba to create this profile . Before creating this profile below steps can be performed to check if the profile already exists. Profiles screen ---> View ---> Query By Example ---> Enter GMF_CONC_DEBUG in Name field Profile ---> View ---> Query By Example ---> Run If the query does not return any records, it means that this profile was not created Use below information create a new record : Name GMF_CONC_DEBUG Application Process Manufacturing Financials User Profile Name GMF: Concurrent Debug Flag Description Debug level flag for GMF concurrent programs Active Dates Enter a date from which this profile is active 2 Find File versions, Profile values and Patches Applied These steps are same in 11i and R12. File versions and Profile values There is a concurrent request named Diagnostics: Apps Check which can be submitted in order to get the file version and profile values. Responsibility : PURCHASING Menu -> View Requests -> Submit a new concurrent request -> Diagnostics: Apps Check Parameter : Process Manufacturing Financials (In order to get multiple product versions, submit different products needed in the parameter.) If your requirement is to find only one form version , it is easier to get that from the Application . These steps are same in 11i and R12. Inside the application select the Menu: Use Help->About Oracle Applications Scroll down to find the form name Character: Use Help->Version If you have the access to the server where the Application is installed use below commands to get the executable file versions
s t r i n g s$ G M F _ T O P / b i n / G M F A C O S T|g r e pH e a d|s o r t
9/25/13
Document 1213193.1
For a particular file version inside the executable

s t r i n g sa$ G M F _ T O P / b i n / G M F A C O S T|g r e pi' $ H e a d e r ' |g r e pg m a f m t . l c
Finding a package version

S E L E C Tn a m e ,t e x t F R O Ma l l _ s o u r c e W H E R EU P P E R( N A M E )L I K EU P P E R( ' % & E n t e r P a c k a g e N a m e % ' ) A N Dt e x tL I K E' % $ H e a d e r % ' O R D E RB Y1 ;
Finding a view definition

S E L E C Tv i e w _ n a m e , t e x tF R O M D B A _ V I E W SW H E R EU P P E R( V I E W _ N A M E )L I K EU P P E R( ' % & E n t e r V i e w N a m e % ' );
Note that in SQL*Plus the output from the above statement will normally be limited to 80 characters. To find out how large the view definition is:
S E L E C Tv i e w _ n a m e , t e x t _ l e n g t hF R O M D B A _ V I E W SW H E R EU P P E R( V I E W _ N A M E )L I K EU P P E R( ' % & E n t e r V i e w N a m e % ' );
You now need to use the SQL*Plus 'SET LONG <xxx>' command, using a number greater than the View Length returned above. So if the query returned a length of '9800':
S Q L > S E TL O N G1 0 0 0 0
... will allow the whole View Definition to be displayed, Patches Applied, File name and Version using Query
S E L E C TD I S T I N C Ta f . a p p _ s h o r t _ n a m e ,a f . f i l e n a m e ,a f v . v e r s i o n , a f v . c r e a t i o n _ d a t e ,a p r . e n d _ d a t e ,a a p . p a t c h _ n a m e ,a p r b . a p p l i e d _ f l a g ,a p r b . s u c c e s s _ f l a g , a . b u g _ n u m b e r F R O Ma d _ p a t c h _ d r i v e r sa p d ,a d _ a p p l i e d _ p a t c h e sa a p ,a d _ p a t c h _ r u n sa p r ,a d _ p a t c h _ r u n _ b u g s a p r b , a d _ p a t c h _ r u n _ b u g _ a c t i o n sa p r b a ,a d _ f i l e _ v e r s i o n sa f v ,a d _ f i l e sa f ,a d _ b u g sa W H E R Ea p d . p a t c h _ d r i v e r _ i d=a p r . p a t c h _ d r i v e r _ i dA N Da p d . a p p l i e d _ p a t c h _ i d= a a p . a p p l i e d _ p a t c h _ i d A N Da p r . p a t c h _ r u n _ i d=a p r b . p a t c h _ r u n _ i dA N Da p r b . p a t c h _ r u n _ b u g _ i d=a p r b a . p a t c h _ r u n _ b u g _ i d A N Da p r b a . p a t c h _ f i l e _ v e r s i o n _ i d=a f v . f i l e _ v e r s i o n _ i dA N Da f v . f i l e _ i d=a f . f i l e _ i d A N Da . b u g _ i d=a p r b . b u g _ i d A N Da f . a p p _ s h o r t _ n a m e=' G M F ' O R D E RB Y4D E S C ;
9/25/13
Document 1213193.1
Note that the above query tells you which patches have specifically been applied on your environment, but it does not list those fixes which came onto your system implicitly when (for example) a consolidated patch or a Patch Set was applied. When given a list of patches, you can find out which ones are already applied on your system (either explicitly or implicitly) with the following script:
S E L E C TB U G _ N U M B E RF R O MA D _ B U G S W H E R EB U G _ N U M B E RI N( ' < P a t c h 1 > ' ,' < P a t c h 2 > ' ,. . . ) ;
When a value of Bug_Number is returned by this script, that patch is already applied and does not need to be applied again. 3 Find Log File and Error messages a) Cost Rollup These steps are same in 11i and R12. Navigation : Standard Costs -> Cost Rollup If the issue is happening for a particular item, run the cost rollup only for that item/product so that we have less data. When a new request is submitted (screen name Start Cost Rollup), note down the reference number. Once the request is completed go to the same Cost Rollup screen and click on the Cancel button. It will show Cost Rollup screen. Query for the reference number. Process status can be found from the Menu ->Actions->Process Status in the same screen. Error messages can be found from the Menu ->Actions->View Error messages. If the error messages are less use the Menu -> Export to get the error messages to an excel file. If there are more error messages please use the below query to get the error messages from the database using the reference number.
S E L E C Tl i n e _ n o ,m e s s a g e _ c o m m e n t ,r o l l u p _ i d F R O Mc m _ r l u p _ m s g W H E R Er o l l u p _ i d=& E n t e r R e f N o O R D E RB Yl i n e _ n o ;
Log file for the Cost Rollup can be seen from Menu -> View Requests ->Find Requests -> Search for the Cost Rollup Concurrent request. Click on the button View Log to get the log file. If the log file is very large, note down the concurrent request id from the Concurrent Requests screen and use it in below query to find the location.
S E L E C Tp h a s e _ c o d e ,s t a t u s _ c o d e ,d e s c r i p t i o n ,c o m p l e t i o n _ t e x t ,l o g f i l e _ n a m e F R O Mf n d _ c o n c u r r e n t _ r e q u e s t s W H E R Er e q u e s t _ i d= & E n t e r R e q u e s t I D ;
If you do not have the access to this file , request your dba to provide the above log file. Provide the file version (Apps Check), log file and error messages for issues related to this.
https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=rhj7sao4j_57&id=1213193.1
4/20
9/25/13
Document 1213193.1
b) Actual Cost Process These steps are same in 11i and R12. Navigation : Actual Costs-> Actual Cost Process When a new request is submitted (screen name Start Actual Cost Process), note down the reference number. Once the request is completed go to the same Actual Cost Process screen and click on the Cancel button. It will show Actual Cost Process screen. Query for the reference number. Process status can be found from the Menu ->Actions->Process Status. Error messages can be found from the Menu ->Actions->View Error messages If the error messages are less use the Menu -> Export to get the error messages. If there are more error messages please use the below query to get the error messages from the database using the reference number.
S E L E C Tl i n e _ n o ,m e s s a g e _ c o m m e n t F R O Mc m _ a c e r _ m s g W H E R Ea c p r o c _ i d=& E n t e r R e f N o O R D E RB Yl i n e _ n o ;
Log file for the Actual Cost Process can be seen from Actual Cost Process screen by clicking on View Log button. Same log file can be seen from Concurrent request screen. Menu -> View Requests ->Find Requests -> Search for the Actual Cost Process Concurrent request. Click on the button View Log to get the log file. If the log file is very large, note down the request id from the Requests screen and use it in below query to find the location.
If you do not have the access to this file , request your dba to provide the above log file. Provide the file version (Apps Check), log file and error messages for issues related to this. c) Lot Cost Process These steps are same in 11i and R12. Navigation : Lot Costs-> Lot Cost Process If the issue is happening for a particular lot or item run the Lot cost process only for that so that we have less data. When a new request is submitted (screen Lot Cost Process), note down the reference number. Process status can not be found from the same screen. It can be found only from the view requests screen. Also there is no view error messages for this process. Log file for the Lot Cost Process can be seen from Concurrent request screen. Menu -> View Requests ->Find Requests -> Search for the Lot Cost Process Concurrent request. Click on the button View Log to get the log file. If the log file is very large, note down the request id from the Requests screen and use it in below query to find the location.
9/25/13
Document 1213193.1
Please note that in case of lot costing unlike other requests there is no error message which can be found from Menu >Actions- >View Error messages. If you do not have the access to this file , request your dba to provide the above log file. Provide the file version (Apps Check) and log file for issues related to this. d) Cost Update 11i Navigation : MAC-> Cost Update R12 Navigation : Cost Update When a new request is submitted (screen name Start Cost Update Process), note down the reference number. Once the request is completed go to the same Cost Update screen and click on the Cancel button. It will show Cost Update Process screen. Query for the reference number. Process status can be found from the Menu ->Actions->Process Status. Error messages can be found from the Menu ->Actions->View Error messages If the error messages are less use the Menu -> Export to get the error messages. If there are more error messages please use the below query to get the error messages from the database using the reference number.
S E L E C Tl i n e _ n o ,m e s s a g e _ c o m m e n t F R O Mc m _ c u p d _ m s g W H E R Ec u p r o c _ i d=& E n t e r R e f N o O R D E RB Yl i n e _ n o ;
Log file for the Cost Update can be seen from Menu -> View Requests ->Find Requests -> Search for the Cost Update Concurrent request. Click on the button View Log to get the log file. If the log file is very large, note down the request id from the Requests screen and use it in below query to find the location.
If you do not have the access to this file , request your dba to provide the above log file. Provide the file version (Apps Check), log file and error messages for issues related to this. e) Test Subledger Update This is available only in 11i Navigation : MAC-> Subledger Update -> Menu -> Actions ->Test Subledger Update If the issue is happening for a particular source, run this process only for that source. If this is happening for a particular date restrict this using the Post Start Date and Post End Date. This helps to have the smallest data that replicates the issue.
9/25/13
Document 1213193.1
When a new request is submitted (screen name Test Subsidiary Ledger Update ), note down the reference number. Once the request is completed go to the same Subsidiary Ledger Update screen and click on the Cancel button. It will show Subsidiary Ledger Update Process screen. Query for the reference number. Process status can be found from the Menu ->Actions->Process Status. Error messages can be found from the Menu ->Actions->View Error messages If the error messages are less use the Menu -> Export to get the error messages. If there are more error messages please use the below query to get the error messages from the database using the reference number.SELECT line_no, message_text
F R O Mg l _ m e s g _ t b l W H E R Er e f e r e n c e _ n o=& E n t e r R e f N o O R D E RB Yl i n e _ n o ;
Log file for the Test Subledger can be seen from Concurrent request screen. Menu -> View Requests ->Find Requests -> Search for the Test Subledger Concurrent request. Click on the button View Log to get the log file. If the log file is very large, note down the request id from the Requests screen and use it in below query to find the location.
If you do not have the access to this file , request your dba to provide the above log file. Provide the file version (Apps Check), log file, report output if any and error messages for issues related to this. f) Final Subledger Update Update This is available only in 11i Navigation : MAC-> Subledger Update -> Menu -> Actions -> Subsidiary Ledger Update. Please note that Final mode can be run only once. So please check if the same issue happens when the Test Subledger is run. If the issue is happening for a particular source, run this process only for that source. If this is happening for a particular date restrict this using the Post Start Date and Post End Date. This helps to have the smallest data that replicates the issue. When a new request is submitted (screen name Subsidiary Ledger Update ), note down the reference number. Once the request is completed go to the same Subsidiary Ledger Update screen and click on the Cancel button. It will show Subsidiary Ledger Update Process screen. Query for the reference number. Process status can be found from the Menu ->Actions->Process Status. Error messages can be found from the Menu ->Actions->View Error messages If the error messages are less use the Menu -> Export to get the error messages. If there are more error messages please use the below query to get the error messages from the database using the reference number.
7/20
9/25/13
Document 1213193.1
S E L E C Tl i n e _ n o ,m e s s a g e _ t e x t F R O Mg l _ m e s g _ t b l W H E R Er e f e r e n c e _ n o=& E n t e r R e f N o O R D E RB Yl i n e _ n o ;
Log file for the Lot Cost Process can be seen from Concurrent request screen. Menu -> View Requests ->Find Requests -> Search for Final Subledger request. Click on the button View Log to get the log file. If the log file is very large, note down the request id from the Requests screen and use it in below query to find the location.
If you do not have the access to this file , request your dba to provide the above log file. Provide the file version (Apps Check), log file, report output if any and error messages for issues related to this. g) Detailed Subledger Report These steps are same in 11i and R12. Navigation : Menu-> View Requests ->Submit New Request -> Detailed Subledger Report Please note that reference number is taken from the Subledger update (11i) or from OPM Accounting preprocessor (R12). If this is happening for a particular date restrict this using the Start Date and End Date. This helps to have the smallest data that replicates the issue. Log file for the Detailed Subledger Report can be seen from Concurrent request screen. Menu -> View Requests >Find Requests -> Search for Detailed Subledger Report . Click on the button View Log to get the log file. If the log file is very large, note down the request id from the Requests screen and use it in below query to find the location.
If you do not have the access to this file , request your dba to provide the above log file. Provide the file version (Apps Check), log file and report output for issues related to this. h) OPM Accounting Pre- Preprocessor This is available only in R12 Navigation : OPM Accounting Preprocessor If the issue is happening for a particular source, run this process only for that source. If this is happening for a particular date restrict this using the Post Start Date and Post End Date. This helps to have the smallest data that replicates the issue. When a new request is submitted (screen name Start OPM Accounting Preprocessor), note down the reference
9/25/13
Document 1213193.1
number. Once the request is completed go to the same OPM Accounting Preprocessor screen and click on the Cancel button. It will show Subsidiary Ledger Update Process screen. Query for the reference number. Process status can be found from the Menu ->Actions->Process Status. Error messages can be found from the Menu ->Actions->View Error messages If the error messages are less use the Menu -> Export to get the error messages. If there are more error messages please use the below query to get the error messages from the database using the reference number.
S E L E C Tl i n e _ n o ,m e s s a g e _ t e x t F R O Mg l _ m e s g _ t b l W H E R Er e f e r e n c e _ n o=& E n t e r R e f N o O R D E RB Yl i n e _ n o ;
Log file for the Test Subledger can be seen from OPM OPM Accounting Preprocessor screen or from the Concurrent request screen. Menu -> View Requests ->Find Requests -> Search for the Test Subledger Concurrent request. Click on the button View Log to get the log file. If the log file is very large, note down the request id from the Requests screen and use it in below query to find the location.
If you do not have the access to this file , request your dba to provide the above log file. Provide the file version (Apps Check), log file and error messages for issues related to this. i) Create Accounting This is available only in R12 Navigation : Menu-> View Requests ->Submit New Request -> Create Accounting Please note that Final mode can be run only once. Make sure to run this in Draft mode and when everything works fine or when you are ready to run the Final run then only run the Create Accounting in Final Mode. If the issue is happening for a particular process category(source), run this process only for that process category(source). If this is happening for a particular date restrict this using End Date. This helps to have the smallest data that replicates the issue. GMF Debug Log mode has no effect on Create Accounting since this is part of SLA which is common for most of the Financial Modules. In order to enable the Debug we need to set FND profile values , run create accounting and run the sql query. Profile values SLA: Enable Diagnostics : Yes FND: Debug Log Enabled : Yes FND: Debug Log Filename: Blank FND: Debug Log Level: Statement FND: Debug Log Module: % These profile values can be set from Menu -> Edit->Preferences ->Profiles->Personal Profile Values (Screen) . Query
9/25/13
Document 1213193.1
for %FND%Debug%. If profile values can not be seen from menu check by logging with the responsibility of system administrator. Otherwise contact your system administrator. Submit Request Run the Create Accounting Program and note down the request id Query Debug output Run the below query in order to get the debug log and upload in excel format:
S E L E C TS U B S T R( m o d u l e ,1 ,7 0 ) ,m e s s a g e _ t e x t ,t i m e s t a m p ,l o g _ s e q u e n c e F R O Mf n d _ l o g _ m e s s a g e sm s g ,f n d _ l o g _ t r a n s a c t i o n _ c o n t e x tt c o n W H E R Em s g . t r a n s a c t i o n _ c o n t e x t _ i d=t c o n . t r a n s a c t i o n _ c o n t e x t _ i d A N Dt c o n . t r a n s a c t i o n _ i d=& E n t e r R e q u e s t I D O R D E RB Yl o g _ s e q u e n c e ;
If you do not have the access to this file , request your dba to provide the above log file. Provide the file version (Apps Check), log file, report output and query output for issues related to this. 4.Enable Forms Trace These steps are same in 11i and R12. Navigation : Menu -> Help ->Diagnostics -> Trace >Trace with Binds and Waits When you enable the trace you can see a Note window which shows the location and file name. Note down this or take a screen shot. This is needed if there is any APP-FND error messages or issues related to List of values or items is reported. Enable the trace just before the error message occurs and Disable the trace once the error message is displayed. Trace can be disabled by Menu-> Help ->Diagnostics -> Trace >No Trace Location of trace files (always on the database server) can be found from below query:
S E L E C T* F R O Mv $ p a r a m e t e r W H E R En a m e=' u s e r _ d u m p _ d e s t ' ;
The following alternative query shows the location and name of trace files relating to currently-running Applications sessions and processes:
S E L E C TD I S T I N C Tp a r . v a l u e| |' / '| |L O W E R ( i n s t a n c e _ n a m e )| |' _ o r a _ '| |s p i d| | ' . t r c '" T r a c ef i l en a m e ",p a r . v a l u e" L o c a t i o n " F R O Mv $ i n s t a n c ei ,v $ p r o c e s sp ,v $ m y s t a tm ,v $ s e s s i o ns ,v $ p a r a m e t e rp a r W H E R Es . p a d d r=p . a d d r A N Ds . s i d=m . s i d A N Dp a r . n a m e = ' u s e r _ d u m p _ d e s t ' ;
Performance Related issues a) Tkprof and Trace If this trace is related to a performance issue please ask your dba to generate the tkprof file using below command.
t k p r o f< f i l e n a m e . t r c >< o u t p u t _ f i l e n a m e >s y s = n oe x p l a i n = a p p s / < p a s s w o r d >
9/25/13
Document 1213193.1
s o r t = ' ( p r s e l a , e x e e l a , f c h e l a ) 'p r i n t = 1 0
b) Tables Analyzed
S E L E C To w n e r ,M I N ( l a s t _ a n a l y z e d ) ,M A X ( l a s t _ a n a l y z e d ) F R O Md b a _ t a b l e s W H E R Eo w n e r=' G M F ' G R O U PB Yo w n e r;
c) Current SQL that is being executed

S E L E C Tr . r e q u e s t _ i d ,s q . s q l _ t e x t ,s s . S I D ,s s . S E R I A L # F R O Mf n d _ c o n c u r r e n t _ r e q u e s t sr ,v $ p r o c e s sp , v $ s e s s i o ns s ,V $ S Q L A R E As q, s q . b u f f e r _ g e t s , s s . l a s t _ c a l l _ e t W H E R Er . r e q u e s t _ i dI N( & E n t e r R e q u e s t I D ) A N Dp . s p i d=r . o r a c l e _ p r o c e s s _ i dA N Ds s . p a d d r=p . a d d r A N Ds q . A D D R E S S=s s . S Q L _ A D D R E S S ;
Run the above every 5 minutes or certain intervals based on how much time the total request takes. This way it is easy to find out which statement is taking time. In some cases we may need to enable trace for the whole application session. Follow below note for the complete steps Note 170223.1 Title: Trace 11i Bind Variables - Profile Option: Initialization SQL Statement - Custom In some cases we may need to enable the trace for the user in order to capture all the SQL statements executed. Follow below note for the complete steps Note 309798.1 How to Trace Specific Database Users to Collect Full DML Statements Executed If you do not have the access to these files , request your dba to provide the above files. Provide the file version (Apps Check), trace file ,log file and screen shots for issues related to this. If this is related to performance issue provide the file version (Apps Check), trace file , log file , tkprof ,table analyzed output and Sql executed output. 5.Enable Reports/Concurrent Request Trace These steps are same in 11i and R12. Responsibility -> System Administrator ->Program ->Define - >Query for the Program name. Enable the checkbox for trace in the Request. And save the record. Once the report is submitted and completed use the same responsibility and navigation path as above to deselect the checkbox. This will disable the trace. Reports/Concurrent request trace location
S E L E C Tf c r . r e q u e s t _ i d" R e q u e s tI D ", f c p . u s e r _ c o n c u r r e n t _ p r o g r a m _ n a m e" P r o g r a m ", p 1 . v a l u e" T r a c eD i r e c t o r y ", ' * ' | | f c r . o r a c l e _ p r o c e s s _ i d | | ' * . t r c '" T r a c eF i l ef o r m a t ", f c p . l a n g u a g e F R O Mf n d _ c o n c u r r e n t _ r e q u e s t sf c r,
9/25/13
Document 1213193.1
v $ p a r a m e t e rp 1, f n d _ c o n c u r r e n t _ p r o g r a m s _ t lf c p W H E R Ep 1 . n a m e= ' u s e r _ d u m p _ d e s t ' A N Df c r . c o n c u r r e n t _ p r o g r a m _ i d=f c p . c o n c u r r e n t _ p r o g r a m _ i d A N Df c r . p r o g r a m _ a p p l i c a t i o n _ i d=f c p . a p p l i c a t i o n _ i d A N Df c r . r e q u e s t _ i d = & E n t e r R e q u e s t I D ;
For example if trace_id = 123567 is returned, then in the user_dump_dest use the following to find the trace file
l sa l* 1 2 3 5 6 7 *
If this trace is related to a performance issue please perform the same steps mentioned in the Performance Related issues under Enable Forms Trace. If you do not have the access to these files , request your dba to provide the above files. Provide the file version (Apps Check), trace file and log file for issues related to this. If this is related to performance issue provide the file version (Apps Check), trace file, tkprof,table analyzed and Sql executed. Concurrent request time taken
s e l e c tf c r . r e q u e s t _ i dr e q u e s t _ i d ,f c p . c o n c u r r e n t _ p r o g r a m _ n a m ec o n c _ p r o g , f c p t . u s e r _ c o n c u r r e n t _ p r o g r a m _ n a m eu s e r _ c o n c _ p r o g ,f c r . a r g u m e n t _ t e x t , f c r . a c t u a l _ s t a r t _ d a t es t a r t _ d a t e ,f c r . a c t u a l _ c o m p l e t i o n _ d a t ec o m p l e t i o n _ d a t e , r o u n d( f c r . a c t u a l _ c o m p l e t i o n _ d a t e-f c r . a c t u a l _ s t a r t _ d a t e ,5 )a a , s u b s t r( n u m t o d s i n t e r v a l( (f c r . a c t u a l _ c o m p l e t i o n _ d a t e -f c r . a c t u a l _ s t a r t _ da t e) ,' d a y ') ,1 2 ,8)D U R A T I O N , f c r . s t a t u s _ c o d e ,f c r . c o m p l e t i o n _ t e x t f r o mf n d _ c o n c u r r e n t _ p r o g r a m sf c p ,f n d _ c o n c u r r e n t _ p r o g r a m s _ t lf c p t , f n d _ c o n c u r r e n t _ r e q u e s t sf c r w h e r ef c r . c o n c u r r e n t _ p r o g r a m _ i d=f c p . c o n c u r r e n t _ p r o g r a m _ i d a n df c r . p r o g r a m _ a p p l i c a t i o n _ i d=f c p . a p p l i c a t i o n _ i d a n df c r . c o n c u r r e n t _ p r o g r a m _ i d=f c p t . c o n c u r r e n t _ p r o g r a m _ i d a n df c r . p r o g r a m _ a p p l i c a t i o n _ i d=f c p t . a p p l i c a t i o n _ i d a n df c p . c o n c u r r e n t _ p r o g r a m _ n a m e= ' & E n t e r S h o r t n a m e ' F o re x a m p l e' G M F A C O S T ' a n dr o w n u m<1 0 0 o r d e rb yt r u n c((( f c r . a c t u a l _ c o m p l e t i o n _ d a t e-f c r . a c t u a l _ s t a r t _ d a t e )/( 1/2 4 ))*6 0) d e s c ;
Modify the above where condition to suit your needs. 6.Important Tables in 11i and R12 a) Important tables in 11i IC_TRAN_PND: Inventory Transaction Table having pending and completed transactions. Transaction types( PORC, XFER, OMSO, PROD ) IC_TRAN_CMP: Inventory Transaction Table having completed transactions.Transaction types( CREI, ADJI, CRER, ADJR, TRNI, TRNR, PIPH ) IC_PERD_BAL: Inventory Table having ending balance, consumption, and yield for closed inventory periods. IC_ITEM_MST_B : Item definition table having all information relating to an item, such as lot/sublot control, unit of measure information, and all class and type designations. CM_CMPT_DTL: Item Cost Component Details table
9/25/13
Document 1213193.1
CM_ACST_LED:-Stores all actual costing transactions GL_ITEM_CST: Cost Details Header table used by Subledger Process. GL_ITEM_DTL: Cost component detail information for the item. GL_SUBR_TST: Subsidiary ledger test run work Table GL_SUBR_LED: Actual Subledger Table or GL subsidiary ledger data GL_SUBR_STA : Subsidiary ledger update state. GL_MESG_TBL: Subledger Error Message Table b) Important tables in R12 MTL_MATERIAL_TRANSACTIONS : Inventory Transaction table which stores a record of every material transaction or cost update performed in Inventory. MTL_TRANSACTION_LOT_NUMBERS: Inventory table which stores lot number information for transactions in the MTL_MATERIAL_TRANSACTIONS table. GMF_MATERIAL_LOT_COST_TXNS : Transaction history table for lot costs MTL_SYSTEM_ITEMS: Item definition table having all information relating to an item, such as lot/sublot control, unit of measure information, and all class and type designations. GMF_PERIOD_BALANCES : OPM Financials table having ending balance, consumption, and yield for closed inventory periods. GL_ITEM_CST: Cost details header table used by Subledger Process. GL_ITEM_DTL: Cost component detail information for the item. GMF_PERIOD_STATUSES :OPM Financails table which stores the OPM Financials period status. CM_MTHD_MST: table stores the cost methods defined GMF_INCOMING_MATERIAL_LAYERS : Layer data for consumption transactions in case of actual cost. GMF_LOT_COST_ADJUSTMENTS: Lot Cost Adjustments header table GMF_XLA_EXTRACT_HEADERS: SLA Extract Headers table which stores transactions for process inventory organizations are processed and all the necessary data for accounting are stored in this table. When the SLA accounting program is run data from this table is extracted for creation of journal entries in SLA. GMF_XLA_EXTRACT_LINES: SLA Extract Lines table which stores transactions for process inventory organizations are processed and all the necessary data for accounting are stored in this table. When the SLA accounting program is run data from this table is extracted for creation of journal entries in SLA. RCV_TRANSACTIONS: stores historical information about receiving transactions XLA_AE_HEADERS: SLA table stores subledger journal entries. There is a one-to-many relationship between accounting events and journal entry headers.
9/25/13
Document 1213193.1
XLA_AE_LINES:SLA table stores the subledger journal entry lines. There is a one-to-many relationship between subledger journal entry headers and subledger journal entry lines. XLA_DISTRIBUTION_LINKS: SLA table stores the link between transactions and Subledger journal entry lines.
7.Important Queries and filtering transaction related issues Please make sure to provide the output in excel format with column headers . For multiple query outputs make sure to take each output in a separate worksheet. These queries are same in 11i and R12 Invalid objects
S E L E C To b j e c t _ n a m e ,o b j e c t _ t y p e ,o w n e r ,s t a t u s F R O Ma l l _ o b j e c t s W H E R Es t a t u s=' I N V A L I D ' ;
Application Instance name, Apps Level, Host Name, Version and database version
S E L E C TD I S T I N C Tf a t . a p p l i c a t i o n _ n a m e" A p p l i c a t i o n " ,f . a p p l i c a t i o n _ i d , a . h o s t _ n a m e ,a . i n s t a n c e _ n a m e ,a . i n s t a n c e _ n u m b e r , a . V E R S I O N" D bV e r s i o n " ,f p g . r e l e a s e _ n a m e " A p p sL e v e l " ,f . p a t c h _ l e v e l" F a m i l yP a c k " F R O M v $ i n s t a n c ea ,f n d _ p r o d u c t _ i n s t a l l a t i o n sf ,f n d _ p r o d u c t _ g r o u p sf p g , f n d _ a p p l i c a t i o n _ t l f a t W H E R Ef . a p p l i c a t i o n _ i d=f a t . a p p l i c a t i o n _ i d A N Df . a p p l i c a t i o n _ i dI N( 5 5 0 ,5 5 1 ,5 5 2 ,5 5 3 ,5 5 4 ,5 5 5 ,5 5 6 ,7 0 9 ,-f o rO P M-r e l a t e d P r o d u c t s 5 0 ,0 ,1 0 1 ,1 7 8 ,2 2 2 ,4 0 1 ,7 2 4 ,7 2 2 ,6 6 0 ,2 0 1 ,6 6 5 ,2 0 0 ) O R D E RB Y1 ;
a) Narrow down transaction related issues in 11i Identify the TRANS_ID from material transactions Inquiry screen in Inventory or provide the ITEM_ID or BATCH_ID in order to narrow down the data Trans_id can be found from Opm Inventory Responsibility under the transaction inquiry Item_id can be found using below query
s e l e c ti t e m _ i df r o mi c _ i t e m _ m s tw h e r ei t e m _ n o=' & E n t e r I t e m N o ' ;
Batch_id can be found from below query

s e l e c t*f r o mg m e _ b a t c h _ h e a d e rw h e r eb a t c h _ n o=' & E n t e r B a t c h n o ' ;
s e l e c t*f r o mi c _ t r a n _ p n dw h e r et r a n s _ i di n( & E n t e r T r a n s I D ) ;
or select * from ic_tran_pnd where item_id in (&EnterItemID); or select * from ic_tran_pnd where item_id in (&EnterBatchID); or select itp.* from ic_tran_pnd itp, ic_item_mst iim where itp.item_id = iim.item_id and item_no in ('&EnterItemNo');
9/25/13
Document 1213193.1
select * from ic_tran_cmp where trans_id in (&EnterTransID); or select * from ic_tran_cmp where item_id in (&EnterItemID); or select itp.* from ic_tran_cmp itc, ic_item_mst iim where itc.item_id = iim.item_id and item_no in ('&EnterItemNo'); select * from cm_mthd_mst where cost_mthd_code = '&EnterCostMethod'; select * from cm_acst_led where item_id in (&EnterItemID); select * from cm_brdn_dtl where item_id= &EnterItemID; select cmp.* from cm_cmpt_mst cmp, cm_cmpt_dtl c where cmp.cost_cmpntcls_id = c.cost_cmpntcls_id and c.calendar_code = '&Entercost_calendar_code' and c.period_code = '&Entercost_period_code' and c.cost_mthd_code = '&Entercost_mthd_code' ; select * from cm_cmpt_dtl where calendar_code = '&Entercost_calendar_code' and period_code = '&Entercost_period_code' and cost_mthd_code = '&Entercost_mthd_code' ; select * from cm_cldr_hdr a where a.calendar_code= '&entercost_calendar_code' select * from cm_cldr_dtl where calendar_code = '&Entercost_calendar_code' and period_code = '&Entercost_period_code' select * from perd_bal where fiscal_year = &EnterFiscalYear and period = &EnterPeriod; select * from gl_item_cst where calendar_code = '&Entercost_calendar_code' and period_code = '&Entercost_period_code' and cost_mthd_code = '&Entercost_mthd_code' ; or select * from gl_item_cst where item_id in (&EnterItemID); select * from gl_item_dtl where itemcost_id in ( select itemcost_id from gl_item_cst where calendar_code = '&Entercost_calendar_code' and period_code = '&Entercost_period_code' and cost_mthd_code = '&Entercost_mthd_code' ); or select * from gl_item_dtl where itemcost_id in ( select itemcost_id from gl_item_cst WHERE item_id in (&EnterItemID ) ); select * from gme_material_details where batch_id = &enterbatchid; select * from gl_subr_led where reference_no=&EnterReferenceNo; or select * from gl_subr_led where doc_id = &EnterBatchID and doc_type='PROD' select * from gl_subr_tst reference_no=&EnterReferenceNo; or select * from gl_subr_tst where doc_id = &EnterBatchID and doc_type='PROD' select * from gl_subr_sta where reference_no=&enterreferenceno; or select * from gl_subr_sta
9/25/13
Document 1213193.1
where doc_id = &EnterBatchID and doc_type='PROD' b) Narrow down transaction related issues in R12 Identify the TRANSACTION_ID from material transactions Inquiry screen in Inventory or provide the INVENTORY_ITEM_ID or BATCH_ID in order to narrow down the data Transaction_id can be found from Opm Inventory Responsibility under the transaction inquiry. Inventory_Item_id can be found using below query
s e l e c td i s t i n c ti n v e n t o r y _ i t e m _ i df r o mm t l _ s y s t e m _ i t e m s w h e r es e g m e n t 1l i k e' % E n t e r I t e m N a m e % ';
Batch_id can be found from below query

s e l e c t*f r o mg m e _ b a t c h _ h e a d e rw h e r eb a t c h _ n o=& E n t e r B a t c h n o;
Enter the transaction dates or the item number and find out the transaction_id
s e l e c tm s i . s e g m e n t 1i t e m n o ,m m t . i n v e n t o r y _ i t e m _ i d ,m m t . t r a n s a c t i o n _ i d , m m t . t r a n s a c t i o n _ d a t e ,m m t . c r e a t i o n _ d a t e ,s y s d a t e f r o mm t l _ m a t e r i a l _ t r a n s a c t i o n sm m t ,m t l _ s y s t e m _ i t e m sm s i w h e r em m t . i n v e n t o r y _ i t e m _ i d=m s i . i n v e n t o r y _ i t e m _ i d a n dm m t . t r a n s a c t i o n _ d a t eb e t w e e n' & E n t e r F r o m D a t e 'a n d' & E n t e r T o D a t e ' o rm s i . s e g m e n t 1=' & E n t e r I t e m N o ' ;
s e l e c t*f r o mm t l _ m a t e r i a l _ t r a n s a c t i o n sm m t w h e r em m t . t r a n s a c t i o n _ i di n( & E n t e r T r a n s a c t i o n I D ) ; o rs e l e c tm m t . *f r o mm t l _ m a t e r i a l _ t r a n s a c t i o n sm m t ,m t l _ s y s t e m _ i t e m sm s i w h e r em m t . i n v e n t o r y _ i t e m _ i d=m s i . i n v e n t o r y _ i t e m _ i d a n dm m t . t r a n s a c t i o n _ d a t eb e t w e e n' & E n t e r F r o m D a t e 'a n d' & E n t e r T o D a t e ' o rm s i . s e g m e n t 1=' & E n t e r I t e m N o ' ; o rs e l e c t*f r o mm t l _ m a t e r i a l _ t r a n s a c t i o n sm m t w h e r em m t . t r a n s a c t i o n _ b a t c h _ i di n( & E n t e r B a t c h I D ) ;
s e l e c t*f r o mm t l _ t r a n s a c t i o n _ l o t _ n u m b e r sm t l n w h e r em t l n . t r a n s a c t i o n _ i di n( & E n t e r T r a n s a c t i o n I D ) ;
OPM Preprocessor Data Run Accounting Preprocessor only for a particular source and small date range to include transaction. This way we have the smallest data that replicates the issue. Reference number is the number obtained while running OPM preprocessor. a)
s e l e c t*f r o mg m f _ x l a _ e x t r a c t _ h e a d e r s w h e r er e f e r e n c e _ n o=' & E n t e r R e f e r e n c e _ n o '
9/25/13
Document 1213193.1
a n dt r a n s a c t i o n _ i di n(& E n t e r T r a n s a c t i o ni d )
b)
s e l e c t*f r o mg m f _ x l a _ e x t r a c t _ l i n e s w h e r eh e a d e r _ i di n(s e l e c th e a d e r _ i df r o mg m f _ x l a _ e x t r a c t _ h e a d e r s w h e r er e f e r e n c e _ n o=' & r e f e r e n c e _ n o 'a n dt r a n s a c t i o n _ i di n(& E n t e r T r a n s a c t i o ni d )) ;
c)
s e l e c tl i n e _ n o , m e s s a g e _ t e x tf r o mg l _ m e s g _ t b l w h e r e( r e f e r e n c e _ n o = ' & r e f e r e n c e _ n o ' ) O r d e rb yl i n e _ n o ;
d ) If this issue is related with Inter org transfer or receiving transaction

s e l e c t*f r o mr c v _ t r a n s a c t i o n s w h e r et r a n s a c t i o n _ i di n( s e l e c tr c v _ t r a n s a c t i o n _ i d f r o mm t l _ m a t e r i a l _ t r a n s a c t i o n s w h e r et r a n s a c t i o n _ i di n( & t r a n s a c t i o ni d ) ) ;
Also provide the debug log output file from the OPM preprocessor. Create Accounting Data SLA Events
s e l e c td l . *f r o mx l a _ e v e n t sd l ,g m f _ x l a _ e x t r a c t _ h e a d e r sg e h w h e r ed l . e v e n t _ i d=g e h . e v e n t _ i d a n dd l . a p p l i c a t i o n _ i d=5 5 5 a n dg e h . e n t i t y _ c o d e=' & E n t e r E n t i t y 'F o rE x a m p l eI N V E N T O R Y a n dg e h . t r a n s a c t i o n _ d a t e< =T O _ D A T E ( ' 0 1 / 0 2 / 0 82 3 : 5 9 : 5 9 ' , ' d d / m m / y y h h 2 4 : m i : s s ' )
SLA Headers
s e l e c ta h . *f r o m x l a _ a e _ l i n e sa l , x l a _ a e _ h e a d e r sa h ,x l a _ d i s t r i b u t i o n _ l i n k sd l , g m f _ x l a _ e x t r a c t _ h e a d e r sg e h ,g m f _ x l a _ e x t r a c t _ l i n e sg e l w h e r ea l . a e _ h e a d e r _ i d=d l . a e _ h e a d e r _ i da n da h . a e _ h e a d e r _ i d=a l . a e _ h e a d e r _ i d a n da h . a p p l i c a t i o n _ i d=5 5 5a n da l . a e _ l i n e _ n u m=d l . a e _ l i n e _ n u m a n dd l . e v e n t _ i d=g e h . e v e n t _ i da n dd l . a p p l i c a t i o n _ i d=5 5 5 a n dd l . s o u r c e _ d i s t r i b u t i o n _ t y p e=g e h . e n t i t y _ c o d e a n dd l . s o u r c e _ d i s t r i b u t i o n _ i d _ n u m _ 1=g e l . l i n e _ i d a n dg e h . h e a d e r _ i d=g e l . h e a d e r _ i da n dg e h . e v e n t _ i d=g e l . e v e n t _ i d a n dg e h . e n t i t y _ c o d e=' & E n t e r E n t i t y 'F o rE x a m p l eI N V E N T O R Y a n dg e h . t r a n s a c t i o n _ d a t e< =T O _ D A T E ( ' 0 1 / 0 2 / 0 82 3 : 5 9 : 5 9 ' , ' d d / m m / y y h h 2 4 : m i : s s ' )
SLA Lines
s e l e c ta l . *f r o mx l a _ a e _ l i n e sa l ,x l a _ a e _ h e a d e r sa h , x l a _ d i s t r i b u t i o n _ l i n k sd l ,g m f _ x l a _ e x t r a c t _ h e a d e r sg e h , g m f _ x l a _ e x t r a c t _ l i n e sg e l
9/25/13
Document 1213193.1
w h e r ea l . a e _ h e a d e r _ i d=d l . a e _ h e a d e r _ i d a n da h . a e _ h e a d e r _ i d=a l . a e _ h e a d e r _ i da n da h . a p p l i c a t i o n _ i d=5 5 5 a n da l . a e _ l i n e _ n u m=d l . a e _ l i n e _ n u ma n dd l . e v e n t _ i d=g e h . e v e n t _ i d a n dd l . a p p l i c a t i o n _ i d=5 5 5a n dd l . s o u r c e _ d i s t r i b u t i o n _ t y p e=g e h . e n t i t y _ c o d e a n dd l . s o u r c e _ d i s t r i b u t i o n _ i d _ n u m _ 1=g e l . l i n e _ i d a n dg e h . h e a d e r _ i d=g e l . h e a d e r _ i da n dg e h . e v e n t _ i d=g e l . e v e n t _ i d a n dg e h . e n t i t y _ c o d e=' & E n t e r E n t i t y 'F o rE x a m p l eI N V E N T O R Y a n dg e h . t r a n s a c t i o n _ d a t e< =T O _ D A T E ( ' 0 1 / 0 2 / 0 82 3 : 5 9 : 5 9 ' , ' d d / m m / y y h h 2 4 : m i : s s ' )
SLA Distributions
s e l e c td l . *f r o mx l a _ a e _ l i n e sa l ,x l a _ a e _ h e a d e r sa h , x l a _ d i s t r i b u t i o n _ l i n k sd l ,g m f _ x l a _ e x t r a c t _ h e a d e r sg e h , g m f _ x l a _ e x t r a c t _ l i n e sg e l w h e r ea l . a e _ h e a d e r _ i d=d l . a e _ h e a d e r _ i da n da h . a e _ h e a d e r _ i d=a l . a e _ h e a d e r _ i d a n da h . a p p l i c a t i o n _ i d=5 5 5a n da l . a e _ l i n e _ n u m=d l . a e _ l i n e _ n u m a n dd l . e v e n t _ i d=g e h . e v e n t _ i da n dd l . a p p l i c a t i o n _ i d=5 5 5 a n dd l . s o u r c e _ d i s t r i b u t i o n _ t y p e=g e h . e n t i t y _ c o d e a n dd l . s o u r c e _ d i s t r i b u t i o n _ i d _ n u m _ 1=g e l . l i n e _ i da n dg e h . h e a d e r _ i d=g e l . h e a d e r _ i d a n dg e h . e v e n t _ i d=g e l . e v e n t _ i d a n dg e h . e n t i t y _ c o d e=' & E n t e r E n t i t y 'F o rE x a m p l eI N V E N T O R Y a n dg e h . t r a n s a c t i o n _ d a t e< =T O _ D A T E ( ' 0 1 / 0 2 / 0 82 3 : 5 9 : 5 9 ' , ' d d / m m / y y h h 2 4 : m i : s s ' )
Accounting entries based on source

S E L E C Tg e h . p m _ b a t c h _ n u m b e r ,g e h . h e a d e r _ i d ,g e h . e v e n t _ c l a s s , g e h . e v e n t _ t y p e ,g e l . l i n e _ n u m b e r ,g e l . j o u r n a l _ l i n e _ t y p e ,c o s t _ c m p n t c l s _ i d , c o s t _ a n a l y s i s _ c o d e ,g e l . c o m p o n e n t _ c o s t ,D E C O D E ( S I G N ( g e l . b a s e _ a m o u n t ) ,1 , g e l . b a s e _ a m o u n t , 0 , 0 , ' ' ) B A S E _ D R _ A M O U N T ,D E C O D E ( S I G N ( g e l . b a s e _ a m o u n t ) , 1 , A B S( g e l . b a s e _ a m o u n t ) , 0 , 0 , ' ' ) B A S E _ C R _ A M O U N T ,D E C O D E ( S I G N ( g e l . t r a n s _ a m o u n t ) ,1 , g e l . t r a n s _ a m o u n t , 0 , 0 , ' ' ) T R A N S _ D R _ A M O U N T , D E C O D E ( S I G N ( g e l . t r a n s _ a m o u n t ) , 1 , A B S ( g e l . t r a n s _ a m o u n t ) , 0 , 0 , ' ' ) T R A N S _ C R _ A M O U N T , g e l . e n t e r e d _ a m o u n t , g e l . a c c o u n t e d _ a m o u n t , F N D _ F L E X _ E X T . G E T _ S E G S ( ' S Q L G L ' ,' G L # ' , g c c . c h a r t _ o f _ a c c o u n t s _ i d , g c c . c o d e _ c o m b i n a t i o n _ i d ) a c c o u n t , G L _ F L E X F I E L D S _ P K G . g e t _ c o n c a t _ d e s c r i p t i o n (g c c . c h a r t _ o f _ a c c o u n t s _ i d , g c c . c o d e _ c o m b i n a t i o n _ i d )a c c _ d e s c r i p t i o n F R O Mg l _ c o d e _ c o m b i n a t i o n sg c c , x l a _ a e _ l i n e sa l , x l a _ d i s t r i b u t i o n _ l i n k sd l , g m f _ s u b l e d g e r _ r e p _ vg e h , g m f _ x l a _ e x t r a c t _ l i n e sg e l W H E R Eg c c . c o d e _ c o m b i n a t i o n _ i d=a l . c o d e _ c o m b i n a t i o n _ i d A N Da l . a e _ h e a d e r _ i d=d l . a e _ h e a d e r _ i dA N Da l . a e _ l i n e _ n u m=d l . a e _ l i n e _ n u m A N Dd l . e v e n t _ i d=g e h . e v e n t _ i dA N Dd l . a p p l i c a t i o n _ i d=5 5 5 A N Dd l . s o u r c e _ d i s t r i b u t i o n _ t y p e=g e h . e n t i t y _ c o d eA N Dd l . s o u r c e _ d i s t r i b u t i o n _ i d _ n u m _ 1= g e l . l i n e _ i d A N Dg e h . h e a d e r _ i d=g e l . h e a d e r _ i dA N Dg e h . e v e n t _ i d=g e l . e v e n t _ i d A N Dg e h . e n t i t y _ c o d e = ' & E n t i t y C o d e ' ;
For eg entity code can be 'REVALUATION' or 'PRODUCTION' or 'PURCHASING' or 'ORDERMANAGEMENT' or 'INVENTORY' -- For batch replace the last line above with below information
A N Dg e h . e n t i t y _ c o d e=' P R O D U C T I O N ' A N Dg e h . p m _ b a t c h _ n u m b e r=' & b a t c h _ n u m b e r '
--If you know the transaction_id use replace the last line with below
18/20
9/25/13
Document 1213193.1
A N Dg e h . t r a n s a c t i o n _ i di n& E n t e r T r a n s a c t i o ni d )
Also provide the FND debug log for the create accounting. Identify transaction Type Transaction type can be identified from the transaction id or item no or inventory item id or date range by using below query.
S E L E C Tm s i . s e g m e n t 1I t e m N a m e ,m t t . t r a n s a c t i o n _ t y p e _ n a m eT x n T y p e ,m m t . * F R O Mm t l _ m a t e r i a l _ t r a n s a c t i o n sm m t ,m t l _ t r a n s a c t i o n _ t y p e sm t t,m t l _ s y s t e m _ i t e m sm s i W H E R Em t t . t r a n s a c t i o n _ t y p e _ i d=m m t . t r a n s a c t i o n _ t y p e _ i d A N Dm t t . t r a n s a c t i o n _ a c t i o n _ i d=m m t . t r a n s a c t i o n _ a c t i o n _ i d A N Dm m t . o r g a n i z a t i o n _ i d = m s i . o r g a n i z a t i o n _ i d A N Dm t t . t r a n s a c t i o n _ s o u r c e _ t y p e _ i d=m m t . t r a n s a c t i o n _ s o u r c e _ t y p e _ i d A N Dm m t . i n v e n t o r y _ i t e m _ i d=m s i . i n v e n t o r y _ i t e m _ i d A N Dm m t . t r a n s a c t i o n _ i di n( & E n t e r T r a n s a c t i o n I D ) ;
or modify the where condition with item_no or inventory_item_id ( msi.segment1 = '&EnterItemNo' or mmt.inventory_item_id= &EnterInventoryItemID) or modify the where condition with date range and mmt.transaction_date between '&EnterFromDate' and '&EnterToDate' 8.Relayering in Actual Cost Process This concept was introduced from 11.5.10 in order to resolve inventory reconciliation issues with batches crossing the period. Prior to this when a batch is completed in one costing period and closed in the next or subsequent period, quantities yielded in prior periods were counted twice in the PMAC cost calculation. This change assumes that the users are creating batch transactions in sequence (like, first consumptions followed by yields) and no back dated transactions. In Release 11i manually-executed scripts were used to recreate the Layer data, but in Release 12 and later a Concurrent Request is provided to make it easier to include the recreation of the Layer Cost data in your routine Period End tasks. Long Name:- GMF Recreate Batch / Period Layers Short Name :- GMFRLAYR Parameters:- Legal Entity, Cost Calendar , Period, Cost Type, Batch Organization & Batch Number This concurrent request is available from patch 8523022 (R12)/ patch 9078278 (R12.1.1) onwards. This can be run for a particular period, batch or organization. Run this request when the batch cost is not correct or when there is transactions which are out of sequence. Actual cost process has to be run after this concurrent request and costs can be verified from the item costs screen. Running this 'Recreate' program can not do any harm, so it is recommended that it should be routinely run before Actual Costing in order to remove potential data problems (for example where the details of a Batch have been updated but these changes are not reflected in the Layer Cost tables. For details of this program in 11i, please refer the following Note - New concurrent program GMF Recreate Batch / Period Layers to recreate layer date for production batches Document ID 1068301.1
19/20
9/25/13
Document 1213193.1
REFERENCES
NOTE:170223.1 - How To Create a User Event Trace by Using Profile Option: Initialization SQL Statement - Custom NOTE:309798.1 - How to Trace Specific Database Users to Collect Full DML Statements Executed
20/20

OPM Financials Trouble Shooting Guide

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

OPM Financials Trouble Shooting Guide

Hochgeladen von

Copyright:

Verfügbare Formate

9/25/13

OPM Financials (GMF) Troubleshooting Guide (Doc ID 1213193.1)

In this Document Purpose Questions and Answers References

QUESTIONS AND ANSWERS

For a particular file version inside the executable

Finding a package version

Finding a view definition

c) Current SQL that is being executed

Batch_id can be found from below query

Batch_id can be found from below query

d ) If this issue is related with Inter org transfer or receiving transaction

Accounting entries based on source

Das könnte Ihnen auch gefallen