sapnote_0001303428-como implementar fileact

2
08.10.2013 Page 1 of 2 SAP Note 1303428 - .par file is missing during FTP transfer Note Language: English Version: 1 Validity: Valid Since 08.02.2009 Summary Symptom You use the SAP Integration Package for SWIFT. If you use the file transfer protocol (FTP) as a transport protocol for FileAct, the parameter files (*.par) are not transferred. Other terms SIPS FTP, file transfer protocol .par FileAct Reason and Prerequisites There is a program error. Solution You require: o XI CONTENT SWIFT 602 /Support Package 06 or XI CONTENT SWIFT 622 /Support Package 00 o The attached corrections You must create a configuration for message split in PI. o Communication channels You require one sender channel and two receiver channels. One receiver channel is required to generate the data file. The other receiver channel is required to generate the parameter file (*.par). Use the module localejbs/swift/FileActConversionToSWIFTModule and set the PI parameter 'DetachParameters' to 'true' in all channels. In the receiver channel for parameter files, we recommend that you set 'Empty-Message Handling' to 'Ignore' so that no empty .par files are generated. For adapter-specific attributes, you must select the file name, directory and file type. o Sender agreement Use the interface SWIFT_payload_parFile in the namespace http://sap.com/xi/SWIFT. o Interface determination

Upload: juan-esteban-cardona-diaz

Post on 22-Oct-2015

109 views

Category:

Documents


2 download

TRANSCRIPT

Page 1: Sapnote_0001303428-Como Implementar FileAct

08.10.2013 Page 1 of 2

SAP Note 1303428 - .par file is missing during FTPtransfer

Note Language: English Version: 1 Validity: Valid Since 08.02.2009

Summary

Symptom

You use the SAP Integration Package for SWIFT. If you use the file transferprotocol (FTP) as a transport protocol for FileAct, the parameter files(*.par) are not transferred.

Other terms

SIPSFTP, file transfer protocol.parFileAct

Reason and Prerequisites

There is a program error.

Solution

You require:

o XI CONTENT SWIFT 602 /Support Package 06 or XI CONTENT SWIFT 622/Support Package 00

o The attached corrections

You must create a configuration for message split in PI.

o Communication channels

You require one sender channel and two receiver channels. Onereceiver channel is required to generate the data file. The otherreceiver channel is required to generate the parameter file(*.par). Use the modulelocalejbs/swift/FileActConversionToSWIFTModule and set the PIparameter 'DetachParameters' to 'true' in all channels.

In the receiver channel for parameter files, we recommend that youset 'Empty-Message Handling' to 'Ignore' so that no empty .parfiles are generated.

For adapter-specific attributes, you must select the file name,directory and file type.

o Sender agreement

Use the interface SWIFT_payload_parFile in the namespacehttp://sap.com/xi/SWIFT.

o Interface determination

Page 2: Sapnote_0001303428-Como Implementar FileAct

08.10.2013 Page 2 of 2

SAP Note 1303428 - .par file is missing during FTPtransfer

Enter the mapping SWIFT_payload_parFile_split. In 700, you mustalso select 'Enhanced' as the interface determination type.

o Receiver agreement

Create a receiver agreement for each of the two receiver channels.Enter the interface SWIFT_payload or SWIFT_parFile. In both cases,the namespace is http://sap.com/xi/SWIFT.

o Receiver determination

The assignment of the interface SWIFT_payload or SWIFT_parFile tothe relevant channels must be displayed in the configurationoverview.

Header Data

Release Status: Released for CustomerReleased on: 20.10.2009 10:01:36Master Language: GermanPriority: Correction with high priorityCategory: Program errorPrimary Component: FIN-FSCM-BNK-SWF SWIFT Integration Package forSAP

Valid Releases

Software Component Release FromRelease

ToRelease

andSubsequent

SWIFT 602 602 602

SWIFT 700 6.22 6.22

SP Patch Level

Software Component Version Support Package SP PatchLevel

SWIFT 602 SP006 000001

SWIFT 622 SP000 000001