How To Know If We Have A GOP ( Global Order Promising ) ATP ( Available To Promise ) License

How To Know If We Have A GOP ( Global Order Promising ) ATP  ( Available To Promise )  License

Basic GOP

–Basic features available as part of Oracle Order Management product

Advanced GOP
–Advanced features that require GOP and ASCP licenses

GOP is not listed as a product in the FND Product List. It gets listed under Advanced Supply Chain Planning ASCP (MSC) product only.
In order to license Global Order Promising you should license the product 'Advanced Supply Chain Planning'  (MSC) in License Manager.
However when you buy licenses you have to select the products you need individually i.e. You have a separate ASCP license and GOP license

You can run the below SQL query to get the output shown below :

select
  fav.application_name app_name
, fav.application_short_name app_s_name
, decode(fpi.status, 'I', 'Yes',
                     'S', 'Shared',
                     'N', 'No', fpi.status) inst_status
, fpi.product_version
, nvl(fpi.patch_level, 'Not Available') patchset
, fav.application_id app_id
from fnd_application_vl fav, fnd_product_installations fpi
where fav.application_id = fpi.application_id
order by 3;

 Alternatively If you run APSCHECK Diagnostic script you will have the same information listed :

Application Name                  Name     Installed?   Prod Version   Patchset        Appl Id
====================== ======== ========== ========================== ============================
Order Management                    ONT      Yes          12.0.0       R12.ONT.B.3         660
Advanced Supply Chain Planning      MSC      Shared       12.0.0       R12.MSC.B.3         724

Pegging Details in ASCP

SELECT mso.sales_order_number, md1.*,
MSI1.ITEM_NAME||' ('||MSI1.INVENTORY_ITEM_ID||')' "COMPONENT (ID)"
, substr( md1.order_number,1,22) order_num
, MS1.NEW_ORDER_QUANTITY COMP_QTY -- this is the pegged or previously pegged column
, decode (ms1.order_type,'1','Purchase order'
,'11','Intransit shipment'
,'12','Intransit receipt'
,'13','Suggested repetitive schedule'
,'14','Discrete job co-product/by-product'
,'15','Nonstandard job by-product'
,'16','Repetitive schedule by-product'
,'17','Planned order co-product/by-product'
,'18','On Hand'
,'2','Purchase requisition'
,'27','Flow schedule'
,'28','Flow schedule by-product'
,'29','Payback Supply'
,'3','Discrete job'
,'30','Current repetitive schedule'
,'32','Returns'
,'4','Suggested aggregate repetitive schedule'
,'41','User Supply'
,'45','Demand Class Consumption'
,'46','Supply Due To Stealing'
,'47','Demand Due To Stealing'
,'48','Supply Adjustment'
,'49','PO Acknowledgment'
,'5','Planned order'
,'50','ATP Aggregate Supply'
,'51','Planned inbound shipment'
,'52','Requested inbound shipment'
,'53','Internal requisition'
,'60','Order Rescheduling Adjustment'
,'7','Non-standard job'
,'70','Maintenance Work Order'
,'8','PO in receiving') Order_type
-- , decode (MFP1.supply_type, 1, 'Purchase Order', 2, 'Purchase Requisition', 3, 'Work Order', 11, 'Intransit Shipment', 12, 'Intransit receipt') Supply_type
-- ,decode (MFP2.supply_type, 1, 'Purchase Order', 2, 'Purchase Requisition', 3, 'Work Order', 11, 'Intransit Shipment', 12, 'Intransit receipt') Supply_type2
, MFP1.demand_quantity
--, MFP1.supply_quantity
, MFP1.demand_date
, MFP1.supply_date
, ROUND(MFP1.ALLOCATED_QUANTITY,1) COMP_ALLOC
, decode(MD1.origination_type, '29','Peg_Fcast','30','Peg_Sales') Pegged_To
, decode (MFP1.DEMAND_ID, -1,'peg_Excess',-2,'Peg_SS') Pegged_To_1
, MFP2.ORGANIZATION_ID
,MFP1.ORGANIZATION_ID
, decode(MD2.origination_type, '29','Peg_Fcast','30','Peg_Sales') Pegged_To_2
, TRUNC(MS1.NEW_SCHEDULE_DATE) COMP_SUP_DUE
, 'X'
, DECODE(MD2.ORDER_NUMBER,NULL
,TO_CHAR(MD2.DEMAND_ID)
,(SUBSTR(MD2.ORDER_NUMBER,1,14)||SUBSTR(MD2.ORDER_NUMBER,42,5))) SO_NUM
, MSI2.ITEM_NAME||' ('||MSI2.INVENTORY_ITEM_ID||')' "ASSEMBLY (ID)"
-- , MSI2.DESCRIPTION
, TO_CHAR(MD2.REQUEST_SHIP_DATE,'DD/MM/YYYY') RDATE
, TRUNC(MD2.USING_ASSEMBLY_DEMAND_DATE) SSDATE
, MD1.Creation_date
, ROUND((MD2.DMD_SATISFIED_DATE-MD2.USING_ASSEMBLY_DEMAND_DATE),1) LATE
, MD2.DEMAND_PRIORITY PRIORITY
, ROUND(MFP2.DEMAND_QUANTITY,1) so_QTY
, ROUND(MFP2.ALLOCATED_QUANTITY,1) WIP_QTY
, TRUNC(MD1.OLD_DEMAND_DATE) ULSD
, TRUNC(MD1.USING_ASSEMBLY_DEMAND_DATE) COMP_DEM_DUE
FROM APPS.MSC_SUPPLIES MS1 -- COMP
, APPS.MSC_SYSTEM_ITEMS MSI1 -- COMP
, APPS.MSC_FULL_PEGGING MFP1 -- COMP
, apps.msc_sales_orders mso
, (SELECT *
FROM APPS.MSC_DEMANDS
WHERE SR_INSTANCE_ID =&1
AND ORGANIZATION_ID =&2
AND PLAN_ID =&3) MD1 -- COMP
, (SELECT *
FROM APPS.MSC_FULL_PEGGING
WHERE SR_INSTANCE_ID =&1
AND ORGANIZATION_ID =&2
AND PLAN_ID =&3) MFP2 -- FG
, (SELECT *
FROM APPS.MSC_DEMANDS
WHERE SR_INSTANCE_ID =&1
AND ORGANIZATION_ID =&2
AND PLAN_ID =&3) MD2 -- FG
, (SELECT *
FROM APPS.MSC_SYSTEM_ITEMS
WHERE SR_INSTANCE_ID = &1
AND ORGANIZATION_ID =&2
AND PLAN_ID =&3) MSI2 -- FG LEVEL
WHERE 1=1
AND MS1.SR_INSTANCE_ID =&1
AND MS1.ORGANIZATION_ID =&2
AND MS1.PLAN_ID =&3
and mso.demand_id=md1.demand_id
AND MSI1.SR_INSTANCE_ID = MS1.SR_INSTANCE_ID
AND MSI1.ORGANIZATION_ID = MS1.ORGANIZATION_ID
AND MSI1.PLAN_ID = MS1.PLAN_ID
AND MSI1.INVENTORY_ITEM_ID = MS1.INVENTORY_ITEM_ID
AND MFP1.SR_INSTANCE_ID = MS1.SR_INSTANCE_ID
AND MFP1.ORGANIZATION_ID = MS1.ORGANIZATION_ID
AND MFP1.PLAN_ID = MS1.PLAN_ID
AND MFP1.TRANSACTION_ID = MS1.TRANSACTION_ID
AND MD1.DEMAND_ID (+) = MFP1.DEMAND_ID
AND MFP2.PEGGING_ID (+) = MFP1.PREV_PEGGING_ID
AND MD2.DEMAND_ID (+) = MFP2.DEMAND_ID
AND MSI2.INVENTORY_ITEM_ID (+) = MFP2.INVENTORY_ITEM_ID
AND MSI1.ITEM_NAME = 'item'
and md1.order_number='ord'
ORDER BY MS1.OLD_SCHEDULE_DATE, MD2.REQUEST_SHIP_DATE

ERR_GET_INSTANCES (ERROR_MSG=No Free partitions available. Contact DBA to create partitions.)

ERR_GET_INSTANCES (ERROR_MSG=No Free partitions available. Contact DBA to create partitions.)

Through System Administrator responsibility > Security > Responsibility Request >Select the group, All MSC Reports
Place cursor in the name column > Click the Green X on the toolbar > In the name  column select, CREATE APS PARTITIONS  (Make sure to select the  correct one)
Save.

Go the Advanced supply chain planner responsibility > other > request > submit a new request > single request
select CREATE APS PARTITIONS
(Make sure to select the correct one NOT Create ATP Partitions)

Use parameters
plan_partition_count = 0
inst_partition_count = 1

This will create the instance partition and allow continued setup.

Concurrent Request/Program tables in Oracle

Tables Used by Concurrent Request Concurrent Program

FND_CONCURRENT_REQUESTS

Contains a complete history of all concurrent requests (both past history and those scheduled to run in the future).

FND_RUN_REQUESTS

Stores information about the reports in a report set that a user submits including the report set’s parameter values.

FND_CONC_REQUEST_ARGUMENTS

Records all arguments passed by Concurrent Managers to concurrent requests as those requests are running.

FND_DUAL

Records when a request does not update any database tables.

FND_CONCURRENT_PROCESSES

Records information about Oracle Applications processes and OS processes.

FND_CONC_STAT_LIST

Collects runtime performance statistics for concurrent requests.

FND_CONC_STAT_SUMMARY

Contains Concurrent Program performance statistics generated by the Purge Concurrent Request program or the manager data program. These programs use the data in FND_CONC_STAT_LIST to compute these statistics।

Unable to Update Invoice Amounts after Running Create Accounting in DRAFT

Qn1:

Invoice Amount field is available for update before "Draft Accounting" but is “greyed out” after running:
Invoice Workbench form>Invoice>Actions>Run Draft Accounting.
Is this the correct functionality?

An1:

The correct functionality is to be able to adjust adjust accounting entries in Payables after the Create Accounting program is run in Draft mode.
To adjust accounting entries, adjust the transaction details and rerun the Create Accounting program.
See more details in the Oracle Payables User Guide.

Qn2:

For non-matched invoices, the invoice distributions appear to be update-able after Draft accounting.
Is it correct, that you update first the invoice distributions and then invoice line?
The invoice header amount can then be updated?

An2:

First, the amount in invoice distributions must be modified (in fact this is the information that will go into accounting entries)
and right after correct the lines or invoice header amounts.

Qn3:

For matched invoices, nothing appears to be update-able after Draft accounting has been run.
Is this correct?


An3:

Since the invoice is matched, distributions of the invoice contain PO information that cannot be changed in this way.
(the matched lines must be discarded to be able to change/modify the amounts)

Resource requirement outside the resource available time (shift) in constrained plans

Resource Requirement Start Date is outside the resource availability (shift times) in an Enforce Demand Capacity Constrained or Enforce Due Date plan with seemingly no resource constraint


1. Go into the responsibility: Process Engineer

2. Navigate to Process Operations > Activity

3. Check the Breakable checkbox against the resource that is seen as causing the problem. 

4. Go into the responsibility: System Administrator

5. Navigate to Profiles > System Profiles

6. Set the profiles as below:

MSO: Schedule across breaks = Yes
MSO: Schedule simultaneous resources across breaks = Yes
MSO: Respect Activity Contiguity Flag for Process Supplies = No

4. Retest the issue by running the ASCP Standard Collection, complete refresh and the ASCP Plan

5. Migrate the solution as appropriate to other environments.

OPM/ASCP such that multiple recipe capacities are respected (production lines)

1) Establish the Recipe Validity Rule Quantities (Minimum, Maximum and Standard) to be all the same for the quantity that can be made by that recipe. So, for the first recipe, all three quantities can be set to 10500, the second as 3500 and the third as 2600. All of the preferences should be the same (1) initially for testing and then can subsequently be different if you prefer making in one line over another

2) Set up the Inventory > Items > Organization Items > General Planning tab > minimum and maximum quantities to the smallest and largest recipe validity rule quantities, so in this example the minimum quantity would be 2600 and the maximum quantity would be 10500. Fixed Days of Supply can be set but all the other order modifiers (e.g. Fixed Lot Multiple) must be unset.

3) The profile MSO: Enable Decision Rules must be set to Yes

4) The ASCP plan needs to be constrained (classic constrained, Enforce Capacity Constraint preferred or With Detailed Scheduling), a manufacturing plan, the Scheduling Zone Minutes Bucket Size in Days must be set to a value within which you want to see change over between recipes, the Use Alternate BOM/ROUTING must be checked in the Decision Rules tab.

If you set up as above and run the ASCP Standard Collection, complete refresh the results in ASCP will allocate the demand quantity to the recipes based on the preferences and the availability of resources and materials and will be correct nine times out of ten (roughly).



The WORKAROUND for this problem is to :

5) Establish a 'planning recipe'. For this you need a formula that includes the product and at least the key ingredients from the existing recipes. You should also establish a route with at least a dummy resource. The recipe validity rule should have a Recipe Use of Planning and a preference of 99 (to ensure it is only used as a last option). The minimum quantity should be set to 2600 and the maximum set to 10500. This quantity range means that, if planned orders are created that do not match the fixed quantities of the production recipes, the 'planning recipe' will be assigned and there at least will be demand for the ingredients created.

MRP Plan Run Hangs On MRCNSP And MRCMON With All Other Requests In Pending Standby

A.  Profile Option Concurrent:Active User Limit or Concurrent:Active Request Limit (short name for sql above is CONC_REQUEST_LIMIT) has a value other than NULL.  This can stop MRP concurrent requests from processing if this is set to too small of a number.  We recommend this profile be set to NULL

B.  There are not enough Standard Manager processes defined.  This is the one we typically run into the most often when MRP concurrent requests are not running or continue to run.  The Standard Manager is a concurrent manager which can be viewed in System Administrator/Concurrent/Manager/Administer.  We recommend the number of processes for this manager based on the following formula:

(2 x <Value for Profile Option MRP: Snapshot Workers>) + 6

So in the example above, if the value of profile option MRP: Snapshot Workers = 5, the formula would be as follows:

(2 x 5) + 6 = 16

To set the number of processes for the Standard Manager navigate System Administrator/Concurrent/Manager/Define - query the Standard Manager - select Workshifts button - set the number of processes - save. Bounce the Standard Manager.  16 would be the minimum to set for the processes on the Standard Manager.  Usually you can add a few more processes to this but generally you would not want to go above 20 - 25. 

Typically the value for profile option MRP: Snapshot Workers is set with 3, 4 or 5 - This enables the Memory Based Snapshot to offload work to the workers to help improve MRP plan performance.

C.  The MRP Manager and/or the Planning Manager are not running (Only for old MRP Planning module.  This does not affect ASCP plans).  If the plan has never been run successfully before and users have loaded demand/supply data into the system without these two being run, then the plan tries to do the Planning Manager work itself if profile MRP:Perform Planning Manager Functions in Loads = Yes while the following profiles are set incorrectly:

MRP:Planning Manager Batch Size = Null
MRP:Planning Manager Max Workers = 10 

Perform the following:

1. Set the following profiles

MRP:Planning Manager Batch Size = 10000
MRP:Planning Manager Max Workers = 0

Save

2. Bounce/Start the MRP Manager in System Administrator/Concurrent/Manager/Administer - find the MRP Manager and start it up. Make sure it comes online with only 1 target/actual process. This manager only runs the Planning Manager and should never be set to more than 1 process. If you have more than one process, change the processes back to 1

3. Start the Planning Manager - Material Planner/Setup/Planning Manager - pick any organization as it doesn't matter. select the Start button.

4. The planning manager has a lot of work to do since it's not been running so it may run for a significant amount of time. When you start to see multiple start messages in the Planning Manager form, this means it's cycling and done with it's work

5. Then run the MRP plan after the Plannning Manager has begun to cycle

D. MRP Manager set to more than 1 process.  As noted above, this Manager should NEVER have more than 1 process.  It's only job is to run the planning manager.  When more than 1 process is setup for this Manager it will then allow multiple Planning Manager concurrent requests.  These requests can then contend with MRP plan concurrent requests and cause them to hang.

1.  Shut down the Planning Manager and MRP Manager

2.  System Administrator/Concurrent/Manager/Define - query MRP Manager - select Specialization Rules button - there should only be 1 row here for the Planning Manager.  If other rows are defined you must move them to a different concurrent manager. 

3.  Then select the Workshifts button - change the processes = 1 - save

4.  Start the MRP Manager and the Planning Manager

5.  Rerun the MRP Plan

set up OPM so that the ASCP Planned Orders are for a fixed quantity

In order for ASCP to generate planned orders in a fixed quantity dependent on the recipe that is being used for the planned order then the Oracle Inventory Organization Item 'Order Modifiers' of Fix Lot Multiple, Fixed Order Quantity and Order Quantity Minimum and Maximum should be NULL for the product.

The Recipe Validity Rule

Process Engineer / Recipes (GMDRCPED)

should be established such that Standard, Minimum and Maximum Quantities are the same and reflect the desired planned order quantity.

This can then be seen in the Collection Workbench Process Effectivity

Advanced Supply Chain Planning/ Advanced Supply Chain Planning/ Collections/ View Collected Data (select the OPM organization), View By Items, Drill down Plans / Collections/ Category, click on the item, right click/ Bom/Routing/ Process Effectivity

as the Minimum and Maximum quantity

and in the Planner Workbench, Supply/Demand in the resultant planned order quantities

This only applies to ASCP Constrained Plans.

Inventory Convergence make any attempt to copy Descriptive Flexfield (DFF)

Does the OPM Migration process for Inventory Convergence make any attempt to copy Descriptive Flexfield (DFF) setup information for an OPM table from the Release 11i database to the corresponding Discrete Inventory table in the Release 12 environment?

We are specifically thinking of a DFF which we have on the OPM Lot Master table (IC_LOTS_MST). In this example would DFF setup and data be copied to MTL_LOT_NUMBERS in the Release 12 environment?

SOLUTION

Provided that there is no data conflict (that is to say, another Descriptive Flexfield already using the relevant 'Attribute' columns in the target table) then the migration process will copy DFF data from the OPM table to the corresponding Discrete Manufacturing (ODM) table.

If there is a data conflict (for example, column ATTRIBUTE1 already used by an existing DFF), then this should be highlighted by the pre-migration report and will need intervention.

Please note, however, that the migration makes no attempt to set up the FND Descriptive Flexfield definition for you in Release 12.  You will need to do this setup (the DFF column names, Value Sets and so on) after the migration is complete.

Oracle VCP- ASCP Staging Tables

select * FROM msc_st_calendars WHERE sr_instance_code = '&enter_sr_instance_code';

select * FROM msc_st_workday_patterns WHERE sr_instance_code = '&enter_sr_instance_code';

select * FROM msc_st_shift_times WHERE sr_instance_code = '&enter_sr_instance_code';

select * FROM msc_st_calendar_exceptions WHERE sr_instance_code = '&enter_sr_instance_code';

select * FROM msc_st_shift_exceptions WHERE sr_instance_code = '&enter_sr_instance_code';

select * FROM msc_st_demand_classes WHERE sr_instance_code = '&enter_sr_instance_code';

select * FROM msc_st_trading_partners WHERE sr_instance_code = '&enter_sr_instance_code';

select * FROM msc_st_trading_partner_sites WHERE sr_instance_code = '&enter_sr_instance_code';

select * FROM msc_st_location_associations WHERE sr_instance_code = '&enter_sr_instance_code';

select * FROM msc_st_planners WHERE sr_instance_code = '&enter_sr_instance_code';

select * FROM msc_st_units_of_measure WHERE sr_instance_code = '&enter_sr_instance_code';

select * FROM msc_st_uom_conversions WHERE sr_instance_code = '&enter_sr_instance_code';

select * FROM msc_st_uom_class_conversions WHERE sr_instance_code = '&enter_sr_instance_code';

select * FROM msc_st_system_items WHERE sr_instance_code = '&enter_sr_instance_code';

select * FROM msc_st_category_sets WHERE sr_instance_code = '&enter_sr_instance_code';

select * FROM msc_st_item_categories WHERE sr_instance_code = '&enter_sr_instance_code';

select * FROM msc_st_resource_groups WHERE sr_instance_code = '&enter_sr_instance_code';

select * FROM msc_st_department_resources WHERE sr_instance_code = '&enter_sr_instance_code';

select * FROM msc_st_resource_shifts WHERE sr_instance_code = '&enter_sr_instance_code';

select * FROM msc_st_routings WHERE sr_instance_code = '&enter_sr_instance_code';

select * FROM msc_st_routing_operations WHERE sr_instance_code = '&enter_sr_instance_code';

select * FROM msc_st_operation_resources WHERE sr_instance_code = '&enter_sr_instance_code';

select * FROM msc_st_boms WHERE sr_instance_code = '&enter_sr_instance_code';

select * FROM msc_st_bom_components WHERE sr_instance_code = '&enter_sr_instance_code';

select * FROM msc_st_supplies WHERE sr_instance_code = '&enter_sr_instance_code' AND order_type = 18;

select * FROM msc_st_safety_stocks WHERE sr_instance_code = '&enter_sr_instance_code';

select * FROM msc_st_item_suppliers WHERE sr_instance_code = '&enter_sr_instance_code';

select * FROM MSC_ST_ITEM_SOURCING WHERE sr_instance_code = '&enter_sr_instance_code';

select * FROM msc_st_interorg_ship_methods WHERE sr_instance_code = '&enter_sr_instance_code';

select * FROM MSC_ST_SR_LOOKUPS WHERE sr_instance_code = '&enter_sr_instance_code';

Move Plan Properties for Oracle HTTP Server

 Move Plan Properties for Oracle HTTP Server

Property	Description	Sample Value
Listen	The Listen address. It can include the host name and port or just the port.	orcl3.example.com:8888 or 8888
User	The Oracle HTTP Server administration user.	admin_user
Group	The group for the user.	admin_group1
ServerAdmin	The administrator's email address.	Webmaster@example.com
ServerName	The name of the server for Oracle HTTP Server. If the host does not have a registered DNS name, use the IP address.	orcl1.example.com
WebLogicHost	The name of the host on which Oracle WebLogic Server is listening for requests.	orcl2.example.com
WebLogicPort	The port number that Oracle WebLogic Server uses to listen for requests.	9002
WebLogicCluster	The name of the host on which an Oracle WebLogic Server cluster is running and its port number.	orcl3.example.com:9003
VirtualHost	The name of the virtual host. The port number listed should also be listed in the Listen directive.	*.8888
PlsqlDatabasePassword	Specific to the PLSQL module, the name of a secure file containing the password. You must provide a password file, even if you are not changing the configuration.	/scratch/orcl/plsql_passwd
PlsqlDatabaseConnectString	Specific to the PLSQL module, the service name of the database.	orcl.example.com:1521:orcl1
PlsqlNLSLanguage	Specific to the PLSQL module, the NLS_LANG variable for the database access descriptor (DAD).	America_America.UTF8
ORAConnectSN	Specific to the oradav module, the Oracle database to which to connect.	db_host:db_port:db_service_name
ORAUser	Specific to the oradav module, the database user (schema) to use when connecting to the service specified by the ORAConnectSN property.	db6175_PORTAL
ORACRYPTPASSWORD	Specific to the oradav module, the absolute path to the secure file containing the password for oradav. You must provide a password file, even if you are not changing the configuration.	/scratch/oracle/dav_passwd
SSLWallet	The location of the SSL wallet, if the wallet is not in the default location.	/scratch/oracle/mw_home/ORACLE_INSTANCE/config/OHS/ohs1/keystores/mywallets
DocumentRoot	The directory that stores the main content for the Web site.	/scratch/oracle/mw_home/ORACLE_INSTANCE/config/ohs/ohs1/htdocs
Alias	The location of the alias, if it is not in the default location. Note that you change the value within the double quotation marks.	/icons/"/scratch/orcl/icons/"
ScriptAlias	The location of the script alias, if it is not in the default location. Note that you change the value within the double quotation marks.	/cgi-bin/"/scratch/oraclcgi-bin/"
WebGateInstalldir	The location of the WebGate installation directory, as specified in the webgate.conf file.	/scratch/oracle/mw_home/Oracle_OAMWebGate1/webgate/ohs

Unable to create new native thread

Unable to create new native thread

Perform all the Steps


Connect as su: UNIX> su - theuser
where "theuser" is the name of Unix user running the processes.
   
Check the current soft and hard max user processes: UNIX> ulimit -Su
UNIX> ulimit -Hu

If you see 1024 as a value of ulimit -Hu, please ensure you have already rebooted a server after setting * hard nproc 16384 in limits.conf.

If you see 16384 as a value of ulimit -Hu but ulimit -Su is still 1024, please go the next step.
     
Increase the max user processes soft limitof the current "theuser" session to 16384: UNIX> ulimit -Su 16384  

Re-check the current max user processes: UNIX> ulimit -Su

You should see 16384, then stop and restart both Admin Server an odi_server1 from the current session, re-test the issue and observe the outcome.

Uncategorized exception during repository access

ODI-10182: Uncategorized exception during repository access.

Cause
The error can occur when connecting to a 12c PDB (pluggable database) using the Oracle SID in the URL, for example:

jdbc:oracle:thin:@<host>:<port>:<sid>
Solution
Connections to pluggable databases require an Oracle Service Name in the URL, such as:

jdbc:oracle:thin:@//<host>:<port>/<service_name>
or
jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=<host>)(PORT=<port>)) (CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=<Pluggable Database Service Name>)))

Alternatively an OCI based connection can be used:

jdbc:oracle:oci8:@<tns_alias>

JDE Technical Interview Questions

1.How many numbers detail sections possible in a report template?
A)Multiple. But the physical page size of report template should not exceed 45 inches in length and width. Report template that exceeds this limit might faces problems at runtime…

2.How many detail sections can be added in a report template using report director?

A)Using the Director, only one detail section can be inserted in the report template. Later RDA can be used to enhance the report template and add extra detail sections

3.How many numbers (max) of Page Header/Page Footer sections possible in a report template?

A) Only one

4.How many numbers (max) of Report Header/Report Footer sections possible in a report template?

A)Only one

5.Can a business view be attached to a Page header section?

A)No. Business views can be attached to details sections only

6.what is the default font used to generate PDF reports in E1?

A)Arial

7.Is it possible to print the attachments that are inserted in the report?

A)No. They are just useful to explain the functionality of the report, any special logic used, documenting the changes etc.,

8.The properties and format of report headers and footers and of page headers and footers are similar to which detail section?

A)Group section

9.Report Templates Vs Batch Versions

A)Report templates are master specifications of the report. It defines the data used, how the data is

Selected , sorted, displayed, and formatted etc.

Batch versions read the master specifications from the associated report template and over ride one or more specification of the report template like:

• Section layout

• Section data selection

• Section event rules

• Section database output

• Section sort sequence

This concept allows creating requirement specific reports (versions) without touching the Master (i.e Report Template). Basically you create one report template and create multiple version by overriding the specifications.

Report Power points:

·      Report template is a Master specification

·      Batch version is a child i.e business need based customization of the Master

JDE Interview Questions

1. What is an Object in JDE? Define Some…
   Traditionally a OneWorld Object was defined as any object created in Object Librarian.
   Ex: Applications, Business Functions,Business Views, UBEs, Data Structures, Tables, Media Objects
2. How do JDE Stores Objects?
   Central Objects
   Provides a central location for managing all OneWorld objects. Only used for Development &  Software deployment.
   Never used at runtime.
3. What are Replicated Objects?
   Replicated Objects are stored in a directory on every workstation and logic server that will run OneWorld
   Built from Central Objects, Deployed via packages (‘point-in-time’ snapshot of selected objects)
   Stored in runtime (TAM vs. RDB) format
4. What are Control Objects?
   Control objects are like buttons on the Form as Control obj. Fields on the Form are also control objects.
   We set control errors on the form design so that it stops the processing of error is set on the control.
5. What are tokens?
   A Token has a One-to-One relationship with the following objects:
   Applications, Business Functions, Business Views, UBEs, Data Structures, Tables, Media Objects and Batch Versions
   The Token is used to minimize the possibility of one user overriding another user’s changes to an object.
   When an  object is checked out and is not already checked out by another user The project receives a Token.
   A Token can be released, switched or inherited.
   The Token is released by the project when the project reaches the status designated by the administrator for release.
   A Token is not released by the project when the object is checked back in.
6. What is OMW?
   As a OneWorld developer I sometimes long for the simple days before XE.  I could check out objects from any environment and check them back into any environment. I could more easily view if an object was checked out and to who and which environment.  I could easily see what objects I personally still had checked out locally. I could also transfer objects from one environment to another with a few mouse clicks. 
   The OMW was designed to replace the old tools we were used to using such as the Object Librarian, Promotion Manager, and Object Transfer.  I believe that the OMW is a great tool when it comes to developing for new projects.  I like the fact that I can group up all of the objects I am working on into a project so I never forget the objects I created or modified for the new module I am creating.  In the old days you would have to keep track of objects in a separate file to give to the CNC guy once it was ready to deploy. Using the old method, how many times do you remember leaving off 1 or 2 objects because you forgot to write them down?
   • Promotion Manager
   • Object Transfer
   • Object Librarian
   • Object Librarian Check-in Log
   • To Hide Object Management Tasks
   • To Provide Better Control of OneWorld Objects
   • To Unify all Development into One Interface
   • To Automate Change Management Process
   • To Provide Detail Logging of Objects
7. What is Check In & Check Out?
   Check In – We send the updated specs to the server. It will replace the specs on the server with the specs which we are doing check in. User will not lose the Token.
   Check Out – It will override the local specs of the object which we are trying to check out. We will get the latest specs from the server. User will get the token
8. What is the difference between GET & Check Out?
   Checking out an object allows you to modify the object and check it back in to Central Objects.  Performing a Get copies the latest specifications to your workstation but does not allow you to check in.  This is similar to erasing a check out for those familiar with previous releases of OneWorld.
9. What are the Object Librarian and Non-Object Librarian Objects?
   Only Object Librarian objects have tokens and Non Object Librarian Objects do not have token.
   non-Object Librarian objects  are based on data source rather than path code.
   One World objects include the following non-Object Librarian objects: 
   • Data dictionary items
   • User defined code items
   • Workflow items
   • Menus
10. What are the required fields when adding an Object?
    Object Name, Description, Product Code, System Code, Object Use