Thursday, 25 July 2019

Inbound Interface in Oracle Apps


Inbound Interface :

Create control file and call sql loader using HOST as executable
/* -----------------------
   || Call SQL Loader Program
   || -----------------------
   || This should be done using the below command.
   || If 0 is returned then it has not worked.  Otherwise the concurrent
   || request ID is returned
   */
  
   FND_FILE.PUT_LINE(FND_FILE.LOG,'Load PO Data : Submitting SQL*Loader');
  
   l_request_id := FND_REQUEST.submit_request ( application => 'EQXX'
                                               ,program     => 'E_PO_SQL_LOADER'
                                               ,description => Data Load script for PO Generic Interface'
                                               ,argument1   => p_data_file
                                               ,argument2   => l_control_file
                                               );
                                                    
  
   IF l_request_id = 0 THEN
      -- Request could not be started => Inform Integration Module and Raise Exception
      RAISE e_submit_loader_error;
   ELSE
      -- Request initialised succesfully => Wait for completion and Check status
      COMMIT; -- This will start the request
  
      FND_FILE.PUT_LINE(FND_FILE.LOG,'Load Data : Waiting for SQL*Loader');
     
      l_dummy := FND_CONCURRENT.wait_for_request ( request_id => l_request_id
                                                 , phase      => l_conc_phase  
                                                 , status     => l_conc_status   
                                                 , dev_phase  => l_conc_dev_phase 
                                                 , dev_status => l_conc_dev_status
                                                 , message    => l_conc_message   
                                                 );

      IF l_dummy = TRUE THEN
         FND_FILE.PUT_LINE(FND_FILE.LOG,'The Concurrent Request has returned TRUE');
      ELSE
         FND_FILE.PUT_LINE(FND_FILE.LOG,'The Concurrent Request has returned FALSE');
      END IF;

      IF UPPER(l_conc_status) IN ('ERROR','WARNING') THEN
         RAISE e_load_error;
      END IF;
   END IF;

   FND_FILE.PUT_LINE(FND_FILE.LOG,'Load PO Data : Source Systems : ' || p_source);

2/ E_PO_SQL_LOADER is concurrent program and acting as executable , and executable type is HOST
3/ HOST program is calling .prog extension program which contains unix script to call sql loader script 
4/ first 4 parameters are reserve for unix shell scripting (from 0 to 4)
5/ Code in prog should be like as below:
# submit SQL*Loader
sqlldr $v_id_pswd control=$EQU_TOP/bin/$v_sqlldr_ctl \
                  data=$v_filename \
                  bad=$EQU_TOP/bin/POSQL_$v_request_id.bad \
                  log=$EQU_TOP/bin/POSQL_$v_request_id.log

where control and data file are coming from concurrent program parameter
eval v_filename=$5
v_sqlldr_ctl=$6
6/ control file should be present in custom top / bin folder
7/ Call concurrent program by fnd_request.submit_Request
   l_request_id := FND_REQUEST.submit_request ( application => 'EXX'
                                               ,program     => 'E_PO_SQL_LOADER'
                                               ,description => ' Data Load script for PO Generic Interface'
                                               ,argument1   => p_data_file
                                               ,argument2   => l_control_file
                                               );
                                                    
8/ After successful execution of loader , data is present in staging tables
9/ Now run the concurrent program that will take data from staging table, put validations and insert into mtl_system_items_interface , mtl_item_categories_interface, PO _headers_interface,po_lines_interface
10 / Then call standard concurrent program to submit from interface to base table
11/ program name : Import Standard Purchase Orders
12/ Import Items
13/Item Organization Assignment


2/ For supplier import :
First create control file and check data file format and then create host program to call .prog file , which will call sql loader and data insert into staging tables
Pre-requisites setup’s are: Payment terms, Pay Groups, CCID, Supplier classifications, Bank Accounts , Employees (if employees have to set up as vendors).
The Interface Tables are:
§  AP_SUPPLIERS_INT
§  AP_SUPPLIER_SITES_INT
§  AP_SUP_SITE_CONTACT_INT

Mandatory Columns:
§  VENDOR_SITE_INTERFACE_ID (ap_supplier_sites_int_s.NEXTVAL) – Supplier Site interface record unique identifier
§  VENDOR_SITE_CODE – Supplier Site name

Interface programs:
1.     Supplier Open Interface Import
2.     Supplier Sites Open Interface Import
3.     Supplier Site Contacts Open Interface Import

The data inserted via these interfaces are automatically populated into TCA tables.
Note: AP_SUPPLIER_INT_REJECTIONS table contains suppliers, sites, contacts rejections information.

3/ For Customer Import
First create control file and check data file format and then create host program to call .prog file , which will call sql loader and data insert into staging tables

   Interface Tables
·           RA_CONTACT_PHONES_INTERFACE
·         RA_CUSTOMER_PROFILES_INTERFACE
·         RA_CUSTOMER_INTERFACE
·         RA_CUSTOMER_BANKS_INTERFACE
·         RA_CUST_PAY_METHOD_INTERFACE

Mandatory columns:
·         ORG_ID
·         ORIG_SYSTEM_CUSTOMER_REF
·         INSERT_UPDATE_FLAG
·         CUSTOMER_NAME
·         CUSTOMER_NUMBER (if you are not using Automatic Customer Numbering)
·         CUSTOMER_STATUS
·         LAST_UPDATED_BY
·         LAST_UPDATE_DATE
·         CREATED_BY
·         CREATION_DATE

Then run the Customer Interface program to validate your imported data and transfer the data to the Customer tables within your system
Customer Interface transfers customer data from the interface tables into the following tables:
·         HZ_CONTACT_POINTS
·         HZ_CUST_ACCT_RELATE_ALL
·         HZ_CUST_ACCT_ROLES
·         HZ_CUST_ACCT_SITES_ALL
·         HZ_CUST_ACCOUNTS
·         HZ_CUST_PROFILE_AMTS
·         RA_CUST_RECEIPT_METHODS
·         HZ_CUST_SITE_USES_ALL
·         HZ_CUSTOMER_PROFILES
·         HZ_LOCATIONS
·         HZ_ORG_CONTACTS
·         HZ_PARTIES
·         HZ_PARTY_SITES
·         HZ_PERSON_PROFILES
·         AP_BANK_ACCOUNT_USES
·         AP_BANK_ACCOUNTS
·         AP_BANK_BRANCHES
The Customer Interface program will not allow updates to the following tables:
·         HZ_CUST_ACCT_RELATE_ALL
·         HZ_CUST_SITE_USES_ALL
·         RA_CUST_RECEIPT_METHODS
·         AP_BANK_ACCOUNT_USES
·         AP_BANK_ACCOUNTS
·         AP_BANK_BRANCHES


Friday, 19 July 2019

How to Use HOST as executable in Oracle apps / Send Mail to Business via mailx utility


How to send mail in oracle : Using Mailx utility : Using HOST as executable
UNIX is the most widely used Operating system for Oracle Apps Implementation. Shell script is default programming language for UNIX. Simply we can say, UNIX host based concurrent program is actually a shell script. Unix host based concurrent program executes all command written in shell script and returns control back to the concurrent manager with the exit code.
Exit code in Unix concurrent program:
§  = 0 – program completed successfully
§  > 0 – program completed in error

Create a UNIX concurrent program which emails a file from a location or concurrent program output to a user using mailx utility Concurrent program parameters,


From
To
CC
BCC
Subject
File Location
Table of Contents
·         Pre-Requisite
·         Step1- Create shell script(.prog)
·         Step2- FTP this file to CUSTOM_TOP/bin path
·         Step3: create a soft link to FNDSPESR
·         Step4: register executable
·         Step 5: register concurrent program
Pre-requisite
You should have a working knowledge of Oracle Apps and Basic knowledge of Unix command.
Software/Hardware environment
§  Oracle apps 11i or R12
§  Putty
§  Winscp
Steps To Register Unix Shell Script As A Concurrent Program
Step 1 – Create shell script (. prog)
Let’s create an executable file first. It is a text file with .prog extension. As per Oracle Apps Developer Guide, the extension should be .prog.
In Unix based concurrent program, first 5 parameters from $0 to $4 are reserved and used by Oracle to pass below information to the shell script. User-defined parameters start from $5 onwards.
Note: This is applicable when there exists a link to fndscpr file.

 
— Standard Parameter—
Below parameters from $0 to $4 are reserved to hold information.
$0: Shell script to be executed
$1: Oracle user/password
$2: Applications user_id
$3: Application user_name
$4: Concurrent program request_id
— User-defined parameters—-
$5 Onwards are the custom parameters.
$5: From
$6: To
$7: CC
$8: BCC
$9: Subject
$10: File Path
Note: some Unix operating system you need to use curly brackets when parameter numbers are two digits {$10} or use Unix SHIFT command to shift parameter to $9 position. Check file below for to understand shift command.
# Name:- xxhost_conc_demo.prog
# Description:- Demo script to send email
# parameters
#  From
#  To
#  CC
#  BCC
#  Subject
#  File Name

echo "print reserved parameter"

echo "0 - Shell Script " $0
echo "1 - Oracle user/password" $1
echo "2 - Applications user id" $2
echo "3 - Application user name" $3
echo "4 - Concurrent program request id" $4

echo

echo "print custom parameter"
echo "5 - From" $5
FROM=$5

echo "6 - To" $6
TO=$6

echo "7 - CC" $7
CC=$7

echo "8 - BCC" $8
BCC=$8

echo "9 - Subject" $9
SUB=$9
shift                     # this shift 10th parameter to 9th position
echo "10 -File Name" $9   # referring 10th parameter as 9th
FILE=$9

# send email using mailx command
echo "Testing Unix Host Based concurernt Program" | mailx -s $SUB -c $CC -b $BCC -r $FROM -a $FILE $TO

Step 2 – FTP this file to $XXCUSTOM_TOP/bin path
FTP this script using WinSCP or FILEZILLA to respective $XXCUSTOM_TOP/bin. Host program executable file always put under /bin directory. Make sure encoding of the script should be in Unix format else you will get an error while running the script 
Login to Unix Server using putty and change file permission to 755 using below command,
chmod 755 xxhost_conc_demo.prog

Above step is required to avoid file permission error, else you will get FND-CP-ESP: Child: exec:: Permission denied error. It happens because Oracle Unix user cannot execute the script.
FND-CP-ESP: Child: exec:: Permission denied
/atech/app/xxcust/12.0.0/bin/xxhost_conc_demo
Program exited with status 1
Step 3 – Create a soft link to FNDCPESR
All parameters to shell script are passed as a single concatenated string. You need to either parse and split these parameters using SED, CUT commands or create a soft link to FNDCPER program. This is a standard utility by the oracle which parses parameter passed to the Unix program from the concurrent program and properly segregates them as $0,$1 .. $n.
ln -s $FND_TOP/bin/fndcpesr  xxhost_conc_demo

Do not include .prog extension.
Step 4 – Register executable
Register executable for the program as shown in below image. Navigation Application Developer–> Define–> Executable.
Execution Method: Host

Execution File Name: 
xxhost_conc_demo ( name of file without .prog extension)
Step 5 – Register Concurrent Program
Navigate and register a concurrent program. Select executable name defined in the previous step.



Sample Log File
Below if log file which will help you to understand the how parameters are passed.
+—————————————————————————+
Current system time is 25-OCT-2017 03:51:03
+—————————————————————————+
print reserved parameter
0 – Shell Script /atech/app/xxcust/12.0.0/bin/xxhost_conc_demo
1 – Oracle user/password APPS/apps
2 – Applications user id 45878
3 – Application user name SHOKEEN
4 – Concurrent program request id 90315090
print custom parameter
5 – From vivek@mydemoserver
6 – To shokeen@gmail.com
7 – CC shokeen@gmail.com
8 – BCC ashokeen@gmail.com
9 – Subject Testing
10 -File Name /home/shokeen/sample_file
+—————————————————————————+
No completion options were requested.