Blog Archive

Saturday, October 12, 2013

PI 7.3 single stack FTP->Proxy scenario along with Development standards with the client.


1.Development procedure with client
   a. Developer documents
   b. Reviewer documents
   a.Dynamically pick file name from sender file adapter in mapping and pass target struture
   b.Access multiple directories from file sender,
   c.Get the information FTP directories with browser and use those in file sender
   d.also information about sproxy(create,regenerate), sxi_monitor, se10 tcodes in ECC system
   e.File content conversion in file sender.

Development Procedure with this client:

Gather functional specification from Functional owner. it consists of Mapping document (xsl sheet), it contains both sender fields and target fields along with mapping logic.

1. Prepare the Technical specification by looking into the Functional specification(some times it is called as RD(Requirement document), Get required technical details(if any missed in functional specification), and mapping clarifications with functional team. For this client Technical specification is called as SDS. it contain all PI ESR and ID configuration objects information . also UTP document(test cases with various input data and PI's output data to receiver, with various sample data, in Most cases 3 test cases).

While preparing  Technical document, Mapping document, UTP(unit test document), we can start development. all these are in parallel process.

send sample test cases/show to functional person, if the output is required format or not, Get the confirmation from them.

Upload all these documents in shared point.

1. FSI ->Functional specification index
2. CDF->Complexity determination form
3. SDS->Software Development specification, in other terms,(technical document)(  Point 4 and 6 documents are attached in this document).
4. MD->Mapping document
5. Issue Log document. ( All issues are logged into this document, when it was rectified from
 functional team/other technical teams)
6. UTP document,
7.Confirmation mail/attachment from functional team

After uploading all documents in shared folder, i.e. specific to your Interface folder, send a mail to your reporter/peer to proceed for next steps

7. he will upload code review check list document
8.Object check list document.

You will receive another mail to check the review documents, as per review docs content, do/modify the changes and update those in documents and again upload in sharepoint and reply to reviewer.

sample snap of above documents

Developer document.

FSS-> This helps us, to start the PI development or not

CEE: &gt  ;helps us, Effort estimation and number hours are to be filled in time sheet

Mapping document by pi( which is extracted from functional document/Requirement document), also we can find sample input test file from sender.


 Issue log document


Review documents
Review of List objects as per standards(including naming standards) by peer


File(FTP)->Proxy( Using the Fixvalues in mapping, Multiple directories in sender, receiver SOAP adaper for proxy, file encoding in sender adapter)

1. First create the target structure as per mapping document. (DT->MT->SI), Activate the service interface in ESR, So we can see this object in SAP ECC system by entering the SPROXY tcode. So ABAPer can start this work. with out waiting for us(PI team).

we can see the same structure as similar to PI System. software components structure. Right client on service interface and generate the proxies.

specify the Package name and prefix as per the Functional specification, it has information about prefix and package name. we need to create new request along with interface number/description.  this transport request is useful at the time of transport this ABAP object. we can see the request again in ECC system, by entering the tcode: se10

2. Create Source, and target structures and mapping documents along with name convention documents. if you do not follow the naming convention, you need to repeat the process again and again to deliver the object.

3. Identifying if any ASMA(adapter specific identifiers are used or not), it this cases, use some constants to test our mapping, By replacing with valid constant, helps us, unit test the message mapping, with out dependent on other objects.

** Use Valid constants(with out User defined functions) for UNIT Testing of the Message mapping.

4. After activating the ESR objects, Create the configuration objects
       a) Create the Configuration Scenario.
       b) Add Business system(Most of the cases abap system), Business component(3rd party systems)
       c) Create /add respective communication channels under the above BS/BC, also in Configuration scenario.
       d) Create Integrated configuration scenario and add this in Configuration scenario. else directly create this object in configuration scenario.

Sample Objects in ESR AND ID as follows,


Note: we used to maintain individual software components for sender and receiver systems, different software component for common objects. each s/w components has it's respective objects. Only common software components has common objects, those are mapping objects, bpm,integration scenarios(modeling).

5.Configuration objects

6.Specify encoding information as shown below, required jar files already deployed on PI system

sample FCC as shown below

Picking files from multiple directories(here same host and port, but sender directories are different)

7.use: ftp://host:port/  in the client browser( by using browser help you can see the below page), so it shows list of sub folder in this path, check with FTP service provide if PI user has right access for these folder and able to archive in archive directory or not.

Dynamically picking file name information in mapping by using below code and picking first 2 chars based on that doing fixvalues to target filed(storage location). So in sender file adapter, we need to enable ASMA->file. (  if you want to pass this file name for receiver file(if you use receiver as FILE adapter and want generate its file name dynamically, use the code as shown below, where arrow pointed).

Sample input and out put as follows.
Input->csv,  see the target payload in ecc system in sxi_monitor, by putting message id search


http://pihost:port/nwa/  ->soa  -> communication channel monitor
1. check if any errors exits for communication channel or not,
2.use ping option for communication channel, to determine if all parameters are configured properly or, if cc is able to access required data as specified locaiton.

Use message monitoing and its log, get the message id, check the same message in receiver system(proxies) by using tcode: sxi_monitor, mesasge id search. You can see message here, if pi sends messages(delivery status success).