How Does the MOAC(Multi Org Access Control) Defaulting Rules Work in EBS R12

       How Does the R12 MOAC Defaulting Rules Work?

1. If the profile option “MO: Security Profile” is not set, then “MO:
   Operating Unit” value is used as the default Operating Unit even if “MO:
   Default Operating Unit” profile is set to a different value.

2. If the profile option “MO: Security Profile” is set and gives access to
   one Operating Unit, the default Operating Unit will return this value even if
   “MO: Default Operating Unit” is set to a different value.

3. If the profile option “MO: Security Profile” is set and gives access to
   multiple Operating Units, then the profile value “MO: Default Operating Unit”
   if set is validated against the list of Operating Units in “MO: Security
   Profile”. If the Operating Unit is included in the security profile then it
   is returned as the default value. Otherwise there is no Operating Unit
   default. Moreover, if the Profile Option “MO: Default Operating Unit” is not
   set, then there is no default Operating Unit.

IMPORTANT PROFILE OPTIONS(MOAC) FOR HRMS, MO Units and GL i.e HR:User Type , HR: Security Profile , HR: Business Group, MO: Security Profile , MO: Operating Unit, MO: Default Operating Unit, GL: Data Access Set , GL Ledger Name & GL Ledger ID,

IMPORTANT PROFILE OPTIONS FOR HRMS, MO Units and GL

HR:User Type

It limits field access on windows shared between Oracle Human Resources and Oracle Payroll. If you do not use Oracle Payroll, it must be set to HR User for all responsibilities. This profile option must be set at responsibility level. If you are using Oracle Payroll then you need to choose HR with Payroll User. Below values can be assigned to this profile option:

• HR User
• HR with Payroll User
• Payroll User
  
  

HR: Security Profile

This profile option restricts the access of the organization, positions and payrolls defined in the security profile. This option is predefined at Site Level with the view-all security profile created for the Setup Business Group.

In case of standard HRMS security “HR: Security Profile” profile option is used for each responsibility.

If the Security Groups Enabled security is used, you must not set up the “HR: Security Profile” profile option. This is set up automatically when you assign security profiles using the Assign Security Profile window.

HR:Business Group

“HR: Business Group “ profile option determines which business group linked to a responsibility. Default one is the Setup Business Group at Site level.

For Standard HRMS security this profile option is automatically set up when you enter the “HR: Security Profile” profile option. This profile option is set for each responsibility.

If the Security Groups are already enabled, then this option is not user-configurable. The business group is determined when you create a security profile assignment using the Assign Security Profile window.

MO: Security Profile

This profile option is set to a responsibility, so that a user can access  multiple operating units.

After the security profiles is defined and run the Security List Maintenance program, you can assign them to responsibilities or users using the “MO: Security Profile” profile option. If you set the “MO: Security Profile” profile option, you can also set the MO: Default Operating Unit profile option to specify a default operating unit.

If the MO: Security Profile is set, then the MO: Operating Unit profile is ignored.

MO: Operating Unit

This profile option is set at the application responsibility, so that user with this responsibility can access one operating unit.

MO: Default Operating Unit

This profile option is used to specify a default operating unit from the list of operating units assigned to your responsibility through the profile options  MO: Operating Unit or MO: Security Profile.

Note: If the MO: Operating Unit is set or you have assigned only one operating unit in the “MO: Security Profile” profile option, then that single operating unit will be your default operating unit.

GL: Data Access Set

The GL: Data Access Set profile option is used in Oracle General Ledger in order to determine the ledgers whose access is given. If you want users to access different ledgers from the same responsibility, you should define a data access set and then assign it to the GL: Data Access Set profile option for each General Ledger responsibility.Multiple ledgers can be grouped that shares the same chart of accounts, calendar, and period type in a data access set or a ledger set.

GL Ledger Name & GL Ledger ID 

This profile is used for assigning the Ledger to a responsibility. This profile option controls the ledger that each sub ledger will use for transaction processing. The ledger assigned to the GL Ledger Name profile option will automatically be assigned to the GL : Data Access Set profile option.

LCM(Landed cost management) as Service(Black Box) Transaction flow step by step guide

BLACK-BOX SERVICE TYPE  LCM TRANSACTION FLOW STEPS

Step1: Responsibility: Purchase Order Super User.

           Navigation: Oracle Purchasing--> Purchase Order--> Purchase Orders.

            Create Purchase Order with LCM enabled Organization.

            Supplier: MATERIAL SUPPLIER

            Supplier Site: Chennai

            Ship to: ICD_LCM_Org (LCM enabled Org.)

            Line: (Item): RMLCMSER001

            (Make sure Inventory Asset flag = Y in this org )
            Quantity: 1 

            Price:2500(INR)

            Receipt Routing = “Standard Receipt”                                 

            Match Approval Level = “2-Way”                         

            Invoice Match Option =“Receipt”->it is mandatory for LCM actual management      

            Destination type =  “Inventory”    
            Save and approve the purchase order.  

Step 2:Responsibility: Purchase Order Super User.

             Navigation: Oracle Purchasing Super User-->Receiving-->Receipts  

             Create a Receipt for the Standard PO created above                        

             Choose Ship To Organization.                              

             Enter “Purchase Order” field as the PO number                               

             Click on “Find” button          

             Select the line and save the record in order to generate the Receipt Number.

Step 3:Responsibility: Purchase Order Super User.

           Navigation: Oracle Purchasing Super User-->View-->Request-->
           Submit a New Request--> “Landed Cost Integration Manager” concurrent program.     

           

Step 4: Responsibility: Landed Cost Management Responsibility.

            Navigation: Landed Cost Management Responsibility-->View-->
      Request-->Submit a New Request-->“Shipments Interface Import” concurrent program.  

Step 5: Responsibility : Landed Cost Management.

            Navigation:  Workbench --> Shipments

            Choose LCM enabled Inventory Organization 

            Click Go

            Click Line Groups

            Group Reference = 15160010 “Receipt Number”

            Click Go          

            LCM Shipment created for the receipt appears at the bottom of the page.

           

 Step 6: Choose “View Landed Cost” from the “Actions” and click on  “Go” button.    

          The “Allocations” page, with detailed information of the landed 

          costs of the shipment  will appear.

Step 7: Responsibility : Payable Super User.

            Navigation: Payable Super User-->Invoices-->Entry-->Invoices

            Create a payable invoice by PO match for creating the Material PO Invoice.

Step 8: Similarly the Payable Invoice is created for Freight Invoice.

            Responsibility : Payable Super User.

            Navigation: Payable Super User-->Invoices-->Entry-->Invoices

Step 9: Alternatively if the Freight charges are changed at the time of 

            creation of Payable Invoice.

              Then create the Invoice with the new Freight charge.

Step 10: Responsibility: Landed Cost Management Responsibility.

             Navigation: Landed Cost Management Responsibility-->View-->
             Request-->Submit a New Request-->“Match Interface Import” 
             concurrent program.
             This Request is for updating the Freight charges in the Landed Cost
             Charge with the new value.

Step 11: In Order to find the new Freight Charges in the Landed Cost

              Responsibility : Landed Cost Management.

              Navigation:  Workbench --> Shipments

              Choose LCM enabled Inventory Organization 

              Click Go

              Click Line Groups

              Group Reference = 15160010 à “Receipt Number”

              Click Go          

          

Step 12: Responsibility: Landed Cost Management Responsibility.

              Navigation: Landed Cost Management Responsibility-->View-->
              Request-->Submit a New Request-->“Submit Pending Shipments”
              concurrent program.

        

   

How to print Attached text file in PO to a Purchase Order Print out ?

function CF_ATTACHFormula return Char is
V_ATTACH Varchar2(32000);
V_LONG_TXT LONG(32000);
begin
  SELECT DLT.LONG_TEXT INTO V_LONG_TXT
  /*AD.SEQ_NUM                  ,
  DCT.USER_NAME               ,
  DAT.USER_NAME               ,
  AD.ATTACHED_DOCUMENT_ID     ,
  DET.USER_ENTITY_NAME        ,
  DAT.NAME                    ,
  D.DOCUMENT_ID               ,
  AD.ENTITY_NAME              ,
  AD.PK1_VALUE                ,
  D.MEDIA_ID                  ,
  D.URL                       ,
  DT.TITLE                    ,
  DLT.LONG_TEXT */
FROM FND_DOCUMENT_DATATYPES DAT,
  FND_DOCUMENT_ENTITIES_TL DET    ,
  FND_DOCUMENTS_TL DT             ,
  FND_DOCUMENTS D                 ,
  FND_DOCUMENT_CATEGORIES_TL DCT  ,
  FND_ATTACHED_DOCUMENTS AD       ,
  FND_DOCUMENTS_LONG_TEXT DLT    ,
  PO_HEADERS_ALL    PHA
WHERE D.DOCUMENT_ID       = AD.DOCUMENT_ID
AND DT.DOCUMENT_ID        = D.DOCUMENT_ID
AND DCT.CATEGORY_ID       = D.CATEGORY_ID
AND D.DATATYPE_ID         = DAT.DATATYPE_ID
AND AD.ENTITY_NAME        = DET.DATA_OBJECT_CODE
AND DLT.MEDIA_ID          = D.MEDIA_ID
AND DAT.NAME              = 'LONG_TEXT'
AND ENTITY_NAME = 'PO_HEADERS'
AND AD.PK1_VALUE  = PHA.PO_HEADER_ID
AND PHA.SEGMENT1 = :PO_ORDER;

DECLARE
   f_line       VARCHAR2 (32000);
   f            UTL_FILE.file_type;
   f_dir        VARCHAR2 (250);
   fname        VARCHAR2 (50);
   Comma1       VARCHAR (10);
   Comma2       VARCHAR (10);
   Comma3       VARCHAR (10);
   Comma4       VARCHAR (10);
   Comma5       VARCHAR (10);
 
BEGIN
   f_dir := '/usr/tmp';
   fname := 'TEST.txt';
   f := UTL_FILE.fopen (f_dir, fname, 'r');

 
   LOOP
      BEGIN
        
          UTL_FILE.get_line (f, f_line);
        EXCEPTION
         WHEN NO_DATA_FOUND
         THEN
            EXIT;
      END;

    
   V_ATTACH := V_ATTACH || CHR(10) ||f_line;
   
   SRW.MESSAGE(10002, V_LONG_TXT);

   ---   DBMS_OUTPUT.put_line(  f_line );

     
   END LOOP;

   UTL_FILE.fclose (f);
   COMMIT;
  
   Return V_ATTACH;
  
END;
end;

How to find OPM Batch Close Variance

Batch Close Variance Checking Code

Select aa.ENTERED_AMOUNT,aa.* from gmf_xla_extract_lines aa

where journal_line_type ='CLS'

and event_id in(select event_id from gmf_xla_extract_headers

where transaction_date >='01-SEP-2014'

and transaction_date <='30-SEP-2015');