You are on page 1of 8

.

Technical Document of PKO03 running before PK


EOD Stack is started

Royal Dutch Shell.


Prepared by: Ranjit Pattnaik
November 2018
Technical documentation based on requirements understanding

DOCUMENT INFORMATION
Title: FM_Design_PKO03_running_before_EOD_started _v1

Project Name: Eve – Release 3

Prepared by: Karthik

Document Version Number: 0.1

Document Version Date: 11/07/2018

Reviewed by:

Review Date:

Distribution List:
From Email Date

Ranjit Pattnaik ranjit.pattnaik@dxc.com 11/07/2018

To Email Action* Due Date

       

* Action Types: Approve, Review, Inform, File, Action Required, Attend Meeting, Other (please specify)

VERSION HISTORY

Prepared /
# Date Modified Reviewed by Approved by Section and Text Revised
by

Ranjit
0.1 11/07/18 Design document created.
Pattnaik

© Copyright 2018 DXC Technology Company. All rights reserved. October 2018 Page | 2
Technical documentation based on requirements understanding

TABLE OF CONTENTS

Table of Contents
DOCUMENT INFORMATION 2

VERSION HISTORY 2

TABLE OF CONTENTS 3

PURPOSE 3

TARGET AUDIENCE 3

TERMINOLOGY AND ABBREVIATIONS 3

REFERENCE DOCUMENTS 4

REQUIREMENTS 5

KEY COMPONENTS AFFECTED 5

Solution overview 5

TRAINING CONSIDERATIONS 7

APPENDICES 7

© Copyright 2018 DXC Technology Company. All rights reserved. October 2018 Page | 3
Technical documentation based on requirements understanding

INTRODUCTION

PURPOSE

This document contains the high level design for the FM that PKO03 MFT send will run along with PK
EOD batch stack instead of separate job from Quartz UI. This new solution can reduce some quartz code,
FM code and reduce independent jobs (here e.g. PKO03_MFT_Send) in Quartz UI.With this solution
scheduling is now Event Driven not time driven.

TARGET AUDIENCE

This document mainly targets solution architects, technical system engineers, and solution developers.

TERMINOLOGY AND ABBREVIATIONS

Term Definition

OPs   Operations
 Dev   Development Environment
   
   
   
   
   

REFERENCE DOCUMENTS

Document name
Code Version Source

© Copyright 2018 DXC Technology Company. All rights reserved. October 2018 Page | 4
Technical documentation based on requirements understanding

REQUIREMENTS

Require Associated
Title Defect #
ment # Req’s

As par the internal requirement that output files


TBD    
shouldn’t be time triggered. 
   
   
   
       

KEY COMPONENTS AFFECTED


Solution overview

Currently PKO03 MFT send is set as time trigger. As par the internal requirement output files should not
be time triggered. So new solution is as a new file manager job will run in between PK ERP posting and
PK03 MFT send. This new solution can help to implement new CL4 OUs (CZ, SK & UK).

It will work when we have C51 and C52 files

PK_GLO03_txn_ERP_Posting                                                                    

               PK_Shell_ERP_Posting_file_Check                                                  

                                PKO04_MFT_Send                         

                                                PKO03_MFT_Send

35873|PK_Shell_ERP_Posting_file_Check |30-OCT-2018 |31-OCT-2018 10:59:16 |31-


OCT-2018 10:59:26 |FINISHED |PS_INSTANCE_1

35874|PKO04_MFT_Send |30-OCT-2018 |31-OCT-2018 10:59:25 |31-OCT-2018


10:59:35 |FINISHED |PS_INSTANCE_1

35875|PKO03_MFT_Send |30-OCT-2018 |31-OCT-2018 10:59:34 |31-OCT-2018


10:59:42 |FINISHED |PS_INSTANCE_1

It will work when we have only C51 file.                                                               

© Copyright 2018 DXC Technology Company. All rights reserved. October 2018 Page | 5
Technical documentation based on requirements understanding

PK_GLO03_txn_ERP_Posting                                                                    

               PK_Shell_ERP_Posting_file_Check                                                                  

                                PKO04_MFT_Send_Only

35876|PK_Shell_ERP_Posting_file_Check |30-OCT-2018 |31-OCT-2018 11:00:49 |31-


OCT-2018 11:00:58 |FINISHED |PS_INSTANCE_1

35877|PKO04_MFT_Send_Only |30-OCT-2018 |31-OCT-2018 11:00:57 |31-OCT-


2018 11:01:02 |FINISHED |PS_INSTANCE_1

If no ERP files are generated then it will not sending.


35878|PK_Shell_ERP_Posting_file_Check |30-OCT-2018 |31-OCT-2018 11:28:34 |31-
OCT-2018 11:28:42 |FINISHED |PS_INSTANCE_1

File manager call internally script files to check how many erp posting files generating and depend up on
the file count it send to mft. The logic is defined as below.

Adding FM logic:

<bean id="PK_GLO03_txn_ERP_Posting"
class="com.hp.rcu.rtsp.filemanager.factory.JobContextFactoryBean">
<property name="centerCode" value="PK" />
<property name="bankCode" value="PK0001" />
<property name="jobName" value="PK_GLO03_txn_ERP_Posting" />
<property name="jobRelationships">
<list>
<bean class="com.hp.rcu.rtsp.filemanager.domain.LookBackRelationship">
<property name="enabled" value="${HonorLookback}" />
<property name="jobContext">
<idref bean="PK_GLO03_accounting_batch" />
</property>
<property name="processDateOffset" value="0d" />
</bean>
<ref bean="PkNonCoreConcurrentJobRelationship" />
</list>
</property>
<property name="timeoutString" value="30min" />
<property name="executionStrategy">
<idref bean="PKO03_txn_ERP_Posting_exec" />
</property>
<property name="onSuccess">
<list>
<idref bean="PK_MvtGatherStatsProcJob" />
<!-- <idref bean="PKO04_MFT_Send" /> -->

© Copyright 2018 DXC Technology Company. All rights reserved. October 2018 Page | 6
Technical documentation based on requirements understanding

<idref bean="PK_Shell_ERP_Posting_file_Check" />


<idref bean="PK_runCopyAccntHistProcJob" />
<idref bean="EOD_PK_Aggregate_batch" />
</list>
</property>
</bean>

<bean id="PK_Shell_ERP_Posting_file_Check" name="PK_Shell_Output_File_Check"


class="com.hp.rcu.rtsp.filemanager.factory.JobContextFactoryBean">
<property name="centerCode" value="PK" />
<property name="bankCode" value="PK0001" />
<property name="jobName" value="PK_Shell_ERP_Posting_file_Check" />
<property name="timeoutString" value="30min" />
<property name="executionStrategy">
<idref bean="PKMFT_Send_exec" />
</property>
</bean>

<bean id="PKO04_MFT_Send" name="PKO04_MFT_Send"


class="com.hp.rcu.rtsp.filemanager.factory.JobContextFactoryBean">
<property name="centerCode" value="PK" />
<property name="bankCode" value="PK0001" />
<property name="jobName" value="PKO04_MFT_Send" />
<property name="timeoutString" value="30min" />
<property name="executionStrategy">
<idref bean="PKO04_MFT_Send_exec" />
</property>
<property name="onSuccess">
<idref bean="PKO03_MFT_Send" />
</property>
</bean>

<bean id="PKO03_MFT_Send" name="PKO03_MFT_Send"


class="com.hp.rcu.rtsp.filemanager.factory.JobContextFactoryBean">
<property name="centerCode" value="PK" />
<property name="bankCode" value="PK0001" />
<property name="jobName" value="PKO03_MFT_Send" />
<property name="timeoutString" value="30min" />
<property name="executionStrategy">
<idref bean="PKO03_MFT_Send_exec" />
</property>
<property name="jobRelationships">
<list>
<bean class="com.hp.rcu.rtsp.filemanager.domain.LookBackRelationship">
<property name="enabled" value="${HonorLookback}" />

© Copyright 2018 DXC Technology Company. All rights reserved. October 2018 Page | 7
Technical documentation based on requirements understanding

<property name="jobContext">
<idref bean="PKO04_MFT_Send" />
</property>
<property name="processDateOffset" value="0d" />
</bean>
<ref bean="PkNonCoreConcurrentJobRelationship" />
</list>
</property>
</bean>
<bean id="PKMFT_Send_exec"
class="com.hp.rcu.rtsp.filemanager.factory.ExecutionStrategyFactory">
<property name="execute" value="$
{OUTBOUND_SCRIPT}/shell_output_file_check.sh" />
<property name="workingDirectory" value="${INBOUND_SCRIPT}/" />
<property name="timeout" value="600000" />
<property name="cmdArgTemplate" value=" pk" />
</bean>

TRAINING CONSIDERATIONS
NA

APPENDICES
NA

© Copyright 2018 DXC Technology Company. All rights reserved. October 2018 Page | 8

You might also like