Came across this video about the new Oracle EBS release 12.2.7.

Informative

Read More

SQL Script to find Concurrent program details with Path, program type, Executable details

SELECT fcp.concurrent_program_id
      ,fcp.concurrent_program_name 
      ,fcpt.user_concurrent_program_name usr_conc_program
      ,fcp.enabled_flag flag
      ,fcp.output_file_type output_TYPE
      ,fe.executable_name
      ,fcp.execution_method_code program_method_code
      ,(SELECT meaning FROM apps.fnd_lookup_values WHERE lookup_code = fcp.execution_method_code AND lookup_type = 'CP_EXECUTION_METHOD_CODE') prog_method
      ,fe.execution_method_code executable_method_code
      ,(SELECT meaning FROM apps.fnd_lookup_values WHERE lookup_code = fe.execution_method_code AND lookup_type = 'CP_EXECUTION_METHOD_CODE') exec_method
      ,fe.execution_file_name
      ,fa.application_short_name
      ,fat.application_name
      ,fa.basepath top
      ,(select value from apps.fnd_env_context where variable_name = fa.basepath and concurrent_process_id = (select max(concurrent_process_id) from apps.fnd_env_context)) ||'/reports/US' path
      ,fcp.creation_date
      ,(select user_name||' : '||description from apps.fnd_user where user_id = fcp.created_by) created_by
      ,fcp.last_update_date
      ,(select user_name||' : '||description from apps.fnd_user where user_id = fcp.last_updated_by) updated_by
FROM apps.fnd_concurrent_programs_tl fcpt
    ,apps.fnd_concurrent_programs    fcp
    ,apps.fnd_executables            fe
    ,apps.fnd_application_tl         fat
    ,apps.fnd_application           fa

WHERE 1 = 1
and fcpt.application_id = fcp.application_id
and fcpt.concurrent_program_id = fcp.concurrent_program_id
and fe.executable_id = fcp.executable_id
and fe.application_id = fa.application_id
and fat.application_id = fa.application_id
AND fcp.enabled_flag = 'Y'
and upper(fcpt.user_concurrent_program_name) = '&prog_name_upper_case'--like '%EVENT%'
; Read More

Yes LPNs can be reused in either same inventory organization or a different organization.
This can be achieved using container public API

Provided the current context of the LPN is issued out of store and there is no pending transaction on that LPN and LPN name is a valid LPN name.

Prior to R12.1.1, oracle was not allowing to re use the LPN once shipped out.

But in certain business case this is necessary to reuse.
Like logistic business they have they container returned to dock or warehouse after delivering to customer and which can be resused, so why not the LPN tagged to that.

As of now there is no functionality in oracle forms using which this can be achieved.
In those cases, this can be achieved by using the below API

apps.wms_container_pub.reuse_lpns
It will Validate the LPN on below points

• It should be issued out of stores. 
• It should have a valid LPN name. 
• There should not be any pending transactions for this LPN.

It derives the contents from WMS_LPN_CONTENTS & WMS_LICENSE_PLATE_NUMBERS. This will update the WMS_LPN_HISTORIES table as well

• It marks the LPN as ‘Defined but not used’ with no Subinventory/Locator. 
• LPN is ready for reuse in the organization provided. 

--SAMPLE API CODE 

prompt Enter License Plate Number which has to be reused accept lpn;

Declare

l_Return_Status Varchar2(1);

l_Msg_Count Number;

l_Msg_Data Varchar2(100);

l_Lpn_Id Number;

l_Clear_Attributes Varchar2(10) := 'Y';

l_Unpack_Inner_Lpns Varchar2(10) := 'N';

l_Clear_Containter_Item_Id Varchar2(10) := 'N';

l_Organization_Id Number := Null;

-- l_License_Plate_Number Varchar2(100) := 'JR1';

l_License_Plate_Number VARCHAR2(100):= '&lpn';

Begin

Select Lpn_Id

Into l_Lpn_Id

From Wms_License_Plate_Numbers

Where License_Plate_Number = l_License_Plate_Number;

Wms_Container_Pub.Reuse_Lpns

(

p_Api_Version => 1,

x_Return_Status => l_Return_Status,

x_Msg_Count => l_Msg_Count,

x_Msg_Data => l_Msg_Data,

p_Lpn_Id => l_Lpn_Id,

p_Clear_Attributes => l_Clear_Attributes,

p_New_Org_Id => l_Organization_Id,

p_Unpack_Inner_Lpns => l_Unpack_Inner_Lpns,

p_Clear_Containter_Item_Id => l_Clear_Containter_Item_Id

);

Commit;

Exception

When Others Then

Dbms_Output.Put_Line('SQLEERM ' || Sqlerrm);

End;

Read More

Very nice illustration of cloud services... Came across this in a LinkedIn post so thought of sharing

Read More

Enabling and disabling a parameter (for taking a valid date) in a concurrent program depending on another parameter

Let’s do this with one example.
There is a concurrent program named XXX Invoice Generation which has 2 parameters
Document Type (Others & Sun Trns) and Date
Date field should be enabled only when the Document Type is Sub Trns or else it should be disabled. Also when the Date parameter is enabled, it should accept only dates

So here we have 2 requirements

1. Enable and Disable the Date parameter based on the value in Document Type parameter
2. Accept only valid dates in Date parameter

So actually to achieve the enable and disable of the Date parameter, we need to have a dummy parameter created which will not be displayed and the same should not be used in the code present in background.

So there will be 3 parameters in the concurrent program

Document Type:

Here in this example the parameter is created as Type and prompt as Document Type which is attached to a value set TEST_TYPE which is of type independent and has the values “Others” and “Sub Trns”.

Dummy1:

This is the Dummy parameter which is created to control the enabling disabling of the Date parameter.
This parameter is attached to a valueset DUMMY1 which is of type independent and has the values “Y”.

Also set default value to populate Y when the Document Type is Sub Trns else NULL
select decode(:$FLEX$.Type,'Sub Trns','Y', null) from dual
So when Document Type is “Sub Trns”, Dummy1 value will be Y or else NULL

Date:

This parameter will behave based on the values in the Dummy1 Parameter

So to achieve this, we need to use a table type valueset where we need to put the validation for validating with Dummy1 parameter value.

So as per the requirement when Document Type is “Sub Trns”, then Date should be enabled which means when Dummy1 value is Y.

Using above setup enabling and disabling of the Date parameter can be achieved.

But we have another requirement is to validate the values entered in Date parameter as a valid date or not.
Normally this could have been validated using a valueset FND_STANDARD_DATE but that is of Validation Type None and we cannot have the enabling and disabling functionality if we use this.
So technically to achieve this, we need to tweek the requirement little bit.

We cannot have a plain valueset which will simply validate whether it’s a valid date or not. Instead, as we are using a table type valueset to trigger the enabling and siabling of the parameter, we have to create and use a view which will hold dates for certain period like in this example, last 6 months and next 6 months date. And pull the dates from the view in the valueset.

So when user enters a date, it will validate with the list of values for date between last and next 6 months and allow to proceed further.

So mentioning below the view created for the same

create or replace view system_date_six_months as

(SELECT (TO_DATE (SYSDATE - 180 + LEVEL, 'DD-MON-RRRR')) date_range

           , (TO_CHAR (SYSDATE - 180 + LEVEL, 'Month, DD RRRR')) date_word

      FROM DUAL CONNECT BY LEVEL <= 360)

Update on achieving the second requirement for validating entered value as a valid date or not in Date parameter.

Normal date condition can be also achieved with valueset type as special and with Validate condition as

FND PLSQL "BEGIN
IF 'AND :$FLEX$.Dummy1' <> 'Y' THEN
NULL;
END IF;
END;"

Read More