HSBC ifile via DMEE

Dear SAP experts,
I'm implementing automatic payments through HSBC using the DMEE facility and HSBC ifile formats, and have issues with complying with the HSBC specification.
1. If I make the DME file comma delimited then SAP puts a comma at the end of the last field in the file, which HSBC advise is unacceptable.
2. If instead I make the file fixed length fields and include the commas as filler items, then I end up with spaces at the end of fields where actual data lengths are variable and the actual content less than the ifile specified field length. HSBC is rejected the spaces even though the field length is in accord with the ifile specifications.
Has anyone managed to get interfaces to HSBC working in accord with IFILE specifications and using DMEE facililites and if so how did you overcome the above.
Hope you can help.
Thank you in advance.
Brian Rowley

Hi Jason,
Can you please send me the HSBC xml file format in . We are having a similar requirement.
Thanks,
Gaby

Similar Messages

[DME] Document about data mapping for HSBC ifile format (PP,ACH, COS)

Dear SAP experts,
I'm implementing an automatic payment module through HSBC in an SAP project.
My customer want to streamline their payments to vendors using automated
payments with HSBC.
I have a document about ifile description which show me information about the
structure and data format in HSBC ifile. I know how to create a DME format tree
but the HSBC format seem to be very complicated, it contains a lots of fields and
a lots of them I don't really understand.
I'm sure that many of you have done this before. Do you have any document about
data mapping for HSBC file format? I have a lot of fields leaving undone so any
relevant documents will be very helpful for me.
Hope you can help.
Thank in advance.
Maxielight.

Hello Maxielight,
I too am working on this IFILE format for transmitting to HSBC for Indian INR payments & am using DMEE.
I'm struggling with a couple of fields in relation to PP.
1st is the 'Record Count' in FIle header, which is just a count of the total number of lines in the file.
2nd is the 'Total number of instructions in batch' in Batch Header section, because I'm trying to count using aggreation via reference node id, but because the Batch Header is level 1 & I need to wait for '2nd Party Details for PP' which is at a lower level I always get an error when I run the check with error 'aggregation not permitted because of field I'm using is lower level, or they are not in the same segment.
I've also tried creating a new segment with 'Delay output' but still get similiar error about the nodes being in differenet segments.
How did you get past this issue?
We are not using COS, instead we will print our own cheques in the office so sorry I cannot offer advise there.
Any advice you can offer would be appreciated.
Thanks,
Steve

HSBC IFILE Format for Supplier Payment

Hi,
Please share your experience / documentation for the development of HSBC ifile format for supplier payment.
Regards

Hello Maxielight,
I too am working on this IFILE format for transmitting to HSBC for Indian INR payments & am using DMEE.
I'm struggling with a couple of fields in relation to PP.
1st is the 'Record Count' in FIle header, which is just a count of the total number of lines in the file.
2nd is the 'Total number of instructions in batch' in Batch Header section, because I'm trying to count using aggreation via reference node id, but because the Batch Header is level 1 & I need to wait for '2nd Party Details for PP' which is at a lower level I always get an error when I run the check with error 'aggregation not permitted because of field I'm using is lower level, or they are not in the same segment.
I've also tried creating a new segment with 'Delay output' but still get similiar error about the nodes being in differenet segments.
How did you get past this issue?
We are not using COS, instead we will print our own cheques in the office so sorry I cannot offer advise there.
Any advice you can offer would be appreciated.
Thanks,
Steve

Advising record (ADV - HSBC form) in DME file could not get email address

Dear all,
I have problems with DME file that Advising record could not get email that is maintained in vendor master data.
Standard communication methods in vendor master data must be Emails.
We use exit module to get this email for below fields:
Email chnl se. flag
Email address
T-code DMEE -> Advising record
(Attributes tab: Mapping procedures is Exit module.
Source tab: value was entered for Exit function)
We test once and got the expected result: email shown on DME file, in advising record.
However, as I rechecked recently, we have no email shown (though Constant value 'ADV' shown).
The form is active by the way.
I do not know if I miss anything in configuration.
Please advise.
Thank you very much.
Rgds,
Linh

Hello Linh,
Did you manage to resolve this. I'm facing the same problem, not able to get the email address.
Can you please provide the function module you used.
Thanks,
Srini

Error in DME file.

Hello,
We are executing a payment run. After payment run is executed a DME file is generated. But somehow not the file is not getting generated and we are getting the below error
File C:\DME0347 cannot be opened.
Message no. BFIBL02182.
Please can someone let me how to generate the file.
BR,
Zulfikar

Dear Zulfikar,
The error message BFIBL02182 normally is showing because the directory that was used when starting the payment media program (for example, in background processing), cannot be read online. You should therefore choose a directory that can be written to and read by different machines.
or If required, the file created can be held within the SAP System (saved in TemSe, not filed in the file system), and therefore protected from external access. The file can be downloaded to the user's file system via DME administration.
You can define the name of the file to be created during the download when you execute the payment media program. The content of the parameters for the file names is then stored in the management data and proposed when you execute the download.
Regards,
Paulo

RFFOIT_FOR: What should I do to obtain the bank number account in the DME?

Hi All,
when the italian Company orders, via DME file, a money transfer for a vendor which isn't European, the file DME, in the record PH, position 61-94, shouldn't contain the iban code of the vendor, but his bank number account.
Instead, the program RFFOIT_FOR tries to fill in the DME file the Iban code which doesn't exsiste in the master data of the foreign vendor...
What should I do to obtain the bank number account in the DME file position 61-94?
Thanks

Try Settings > General > Reset > Reset Network Settings on your device.
Note you may have to re-enter stored Wi-Fi passwords after using this feature.
tt2

How to get the international version address in Payment Medium

Hi,
I am trying to output the payment medium for auto-payment, and I need to get the company name information from the vendor master data. As we are in China, we maintained the Chinese name description in the international version, and English name in the normal name field. My question is how i can get the Chinese name when I set up the payment format via DMEE? thx very much~!

Kerry, Were you able to find a solution? If so, can you share your knowledge?

Payment program (RFFOAU_T)

Hi,
Can any one please let me know the functionality of payment program and use of this program.
Thanks in advance.

Short text
Payment Medium for Australia - Bank Transfers/Debit Memo BECS
Description
The program issues data medium exchange in BECS, the disk format used by Australian banks.
As well as the payment media, the accompanying payment advice notes, data medium accompanying sheets and payment summaries can also be printed in one program run.
Requirements
Payment Program Configuration
The parameters that control the way in which the payment medium programs function are configured in Customizing. For more information on configuring the payment program, refer to the Implementation Guide.
Configure payment program
1. Here you need to make specifications for the paying company code. To do this, select the relevant paying company code by choosing Paying Company Codes ->.
If payment advices are to be printed, define a SAPscript payment advice form for use with all company code payment methods. You will find the form F110_IN_AVIS as an example in the standard system.
You need to create and enter text modules in which the texts for the header, footer, signature and sender are stored. These modules can be included in the forms when they are used. To do this, choose Sender Details, from where you can also branch into text maintenance by selecting the modules. The names of the text can be defined by the user, for example F_0001_HEADER for the letter header in company code 0001.
Proceed
2. Here you need to allocate the name of the payment medium program RFFOAU_T to the payment method to avoid incorrect payment media being issued with another program by mistake.
To do this, first choose Payment methods in country, then select the country of your paying company code and the payment method you require, and then maintain the data necessary for printing the form.
Proceed
3. Here you need to make company code specifications for the payment method. To do this, choose Payment Methods In Company Code, then select the paying company code and the payment method. In this menu maintain the following data by choosing Form data or Payment Advice Control:
The SAPscript form for accompanying sheets (F110_AU_BECS in the standard system) as the next form (for DME).
The issuer data.
Sorting the correspondence.
Sorting the line items.
Proceed
Note: You should fill out the issuer specifications as follows:
Line 1 Issuer's name (26 characters long)
Line 4 Issuer's city
4. You need to make further specifications for creating the payment medium in Customizing of the house banks. Select the relevant paying company code by choosing House Banks. In the maintenance of the house banks select your house bank and then maintain the required data via the button Data Medium Exchange. For more details refer to the online documentation for the relevant fields.
Proceed
Notes:
a) Common BSB numbers, which give a bank a unique identification, must be maintained for Australian banks. This three-character abbreviation is defined in the publication 'BSB Numbers in Australia', and is entered in the SAP system as part of the DME data maintenance in the field Altern. bank ID.
b) You need to maintain the lead days. The processing date (batch due date) is calculated from the posting date plus the lead days.
c) The company number (user identification number) is also transferred from the house bank's DME data.
Setting up and changing the SAPscript forms (layout sets)
The following describes the layout of the SAPscript forms in brief. If the forms available in the standard system are sufficient for your requirements, you can skip this part of the documentation.
You can find further information on forms and the SAPscript editor in the guides on styles and form maintenance and word-processing in the SAPscript editor: Select the menu path Help -> SAP Library.
1. When setting up SAPscript forms (layout sets), symbols are included in the text; these are then replaced by actual values when the payment medium programs are run. The fields which can be used for this are defined in the Repository and contained in the following structures:
REGUH Settlement data from the payment program
REGUP Edited invoice items from the payment program
REGUD Formatted data for printing the forms
SPELL Amounts and digits in words.
FSABE Data on accounting clerk.
2. If you want the document long text for an accounting invoice document to be printed on the payment advice form, you must make the following enhancement in element "Long text for invoice document" (specially designed for this purpose):
/: DEFINE &TXT& := '&REGUP-BUKRS()&&REGUP-BELNR(RF0)&&REGUP-GJAHR&'
/: INCLUDE &TXT& OBJECT BELEG ID xyz
The text ID that you must enter for this text (xyz) is defined in the configuration menu and can be read from there. In the standard system, text ID 0003 is predefined for the payment advice information.
Proceed
3. Layout of the payment advice form (F110_IN_AVIS in the standard system)
Pages
FIRST First page per payment advice
NEXT Subsequent pages if page overflow
EDI List of payment advice notes sent per EDI
LAST Form summary section per house bank
Windows and elements
HEADER Letter header
ADDRESS Sender and address of the payee
PAGE Page counter
INFODate, payment document number, etc.
INFO      605Account number of the sender at the recipient
INFO2 Information on the next pages
REPEAT Information for the test print or proposal run
MAIN Form of address before the letter
MAIN      610-x Short text for payment method x
MAIN      610 Letter when 610-x is missing
MAIN      612Alternative payee
MAIN      613 Notification takes place in order
MAIN      614 Signature
MAIN      615 Heading of the invoice item information
MAIN      620 Carryforward at page top after page overflow
MAIN      625Invoice item information
MAIN      625-TXLong text for invoice
MAIN      625-HRInformation line for Payroll Accounting
MAIN      630Sum total
MAIN      631 User-defined text after invoice items
MAIN      675 Header for EDI advices
MAIN      676List of EDI advices
TOTAL     630 Sum total of fixed items
CARRYFWD 635 Carryforward at page bottom for page overflow
FOOTER Letter footer
SUMMARY Form summary section
4. Layout of the data medium accompanying sheet (F110_AU_BECS in the standard system)
Pages
DME Accompanying sheet
LAST Form summary section for each house bank
Windows and elements
DOMESTIC 535 Accompanying sheet
Check that the SAPscript forms (layout sets) which you use have the layout described and, in addition, check that the forms are active (both in the original language as well as in all languages into which the forms were translated).
Proceed
Periodic processing
Before the payment medium programs can be started, the payment program run must have been successfully completed. Check the status of the payment run, or schedule the payment medium programs by specifying one or more variants.
Proceed
Note: If you want to use th 'Payment document update' option, the payment documents must be updated between the time of the payment program run and the time of the payment medium program run.
Output
Forms and lists
Printout files are created per company code and house bank. These can either be printed via the print manager or immediately. Depending on the parameter you select, you can print out one or more of the following:
Accompanying sheet for the payment medium
Payment advice notes (if the information cannot be sent via EDI)
Payment summary
Error log
The number of output files is specified in the flow trace; this makes finding and allocating them within the print manager easier.
Proceed
Note: If the program was started online, then you reach the print manager from the list by selecting one of the output files displayed.
Payment Advice Notes
In addition to being able to print payment advice notes, you can also send these via EDI, fax or email.
1. To send a business partner a payment advice note via EDI, you need to select the indicator Payment advice note per EDI and maintain the partner agreement on screen "Payment Transactions Accounting" in the master record.
Proceed
Using an external converter, the IDoc created by the program can be converted into the EDI format you require (REMADV for example) and then sent.
2. To send a business partner a payment advice note by fax or email, you must use the process interface 00002040 (Business Transaction Events) to define the selection of the message type (printout, fax or email). Before you can do this, however, you must have carried out the necessary technical (Basis) settings for faxing or sending emails.
Process interface 00002050 can also be used to change or configure the print parameters and the parameters for optical archiving for payment advice notes.
DME
Data medium exchange in this case involves the creation of a file which corresponds to the rules of the credit institution in question for automatic payment transactions and which contains all the necessary payment information.
The information relevant for the payment medium (file format, creation data, payment amount in local currency, payment documents involved etc.) are stored in the system and can be called up via the DME manager.
Other functions of the DME manager are:
Downloading the file into your local (PC) file system
Displaying and printing the file contents
Generating a payment summary for the data medium
Proceed
You will find further information about the structure of the data medium in the technical description.
Output in the file system
If required, the file can be written into the file system. The file created can be copied onto a PC via the DME manager. When doing this, you should search for files by download since the data medium is not managed within the SAP System but has already been stored in the file system by means of the payment medium program.
Proceed
If the file name is not to be specified by parameter, then it is generated by the program. It then consists of the disk format, date and time of creation as well as a consecutive number so that the file name in the file system is unique.
If the file name is specified by the user, then a consecutive number is likewise added for each program run. From an organizational point of view, however, you should make sure that already existing files are not overwritten.
Note: If you cannot find the file via the DME manager, then this can be due to the following reason: the directory which was written to when the payment medium program was started (for example, in background processing), cannot be read online. Therefore you should choose a directory which can be written to and read by different machines.
Due to the above-mentioned problems and the affect this has an data security, it is advisable not to write data to the file system. It may be advisable to use this method in cases where the data medium file is 'picked up' from the file system by an external program to be passed on to the bank.
Output in the TemSe
If required, the file created can be stored within the SAP System (stored in the TemSe and not in the file system), thus protecting it from unauthorized external access. You can download the file into the user's file system via DME management.
The name of the file to be created during the download can be determined when running the payment medium program; the contents of the file name parameter are stored in the management data and defaulted when running the download.
Proceed
User exit
You can modify the dataset for data medium exchange by using the user exit interface defined. You can, however, only change the fields of the DTAMAU0 structure.
Creating a user exit
The print program calls up the EXIT_RFFOEXIT_210 function module. Please take the input and output parameters for the user exit from the function module interface.
Proceed
Create an include file with the name ZXFORU32 to program the modifications required.
Proceed
The file is included in the EXIT_RFFOEXIT_210 function module. Use the Enhancements transaction for activating or deactivating your user exits by activating or deactivating the RFFOX210 project affected.
Proceed
Error messages and error log
Termination of processing
You can find out the reason why processing was terminated (for example, production run not yet carried out, form does not exist or is not active) by looking at the error message or the related long text.
Internal SAPscript error
Check the layout of the forms. It must fulfil the above-mentioned conditions. You cannot, for example, create a bank transfer with the check print program, since bank transfers and checks have a completely different layout structure.
Error log
If errors which do not terminate the payment medium program occur when creating the output, the system lists them in the error log. If such a log is created, you must look it over because only you can decide whether the payment medium or payment advices are useless due to the errors the system finds, and decide whether they must be recreated after the errors have been rectified.
During background processing, the system outputs the error log twice, in the flow trace for the job and in a printout file. The flow trace contains information on how to rectify the errors (from the error message long texts).
You can display the long text online by choosing the error log from the list of generated output files and then the error message in question.
plz reward points if dis helps

Bank charges for DD

Dear All,
My client would like to send DD (Demand draft) to vendor and bank charges are bing made by my client. So, to be able to achieve in SAP Configuration where i have to configure (In FBZP) or where else.
they are using APP (F110) how the bank chareges are picked up from APP.
Poings will be assigned.
With best regards
Venkat.

Hi,
setup for debiting bank charges while carrying out F110 payment runs, Instead, I'd used the fields in the House Bank (txn FI12 under Data medium exchange section for Charges account).
Here you specify the Bank no. and the account no. at that bank, which will tell your Bank from which account to debit the charges. What is noteworthy here is that F110 was not used to debit charges, rather instructions were sent to the Bank (via DME) to debit charges (based upon pre-defined and agreed upon rates & categories, etc.).
To complete the setup, there's another field we were using - Control Key in the same section just below the Charges Bank no. and account no. This field has specific usage in some countries (check F1 help on this field), and for all other countries, you can use the field for any account-specific information. We used this to send an indicator to our Bank specifying on what terms to debit charges - like, sending party pays charges, receiving party pays charges, or charges are borne equally by both sending and receiving party.
Sending party - Payer of Funds
Receiving party - Beneficiary of Funds
For your original approach, I hope you've done the settings in txn OBXK - Maintain FI config. - automatic postings for bank charges. The system posts the charges amount you specify for a bank item when settling payment to these accounts. The bank charges accounts must be defined as relevant to cash flow.
Regards,
Viswa

Posting to Bank Acount

Hi Gurus,
Request your advice on this one.
After payroll posting run, the GL linked /559 wagetype is populated. What is the best way to transfer the amount in this to the GL of bank account automatically. i.e Debit the GL linked to /559 wagetype and Credit the company bank GL.
One way to do this is through FB50, but am looking for a more automated solution
Is this possible via DME ? if so how and what is the configuration required ? Would appreciate being linked to some useful information.
Warm Regards
Sanchit

Dear Expert,
Please help me to resolved the following scenario:
   Issue:
   The issue is related to reconciliation of information, for the employeesu2019 claims (LTA, Journals, Driver Allowance, Leave encashment, advances). The payments related to such claims get credited to Wages payable a/c (GL a/c 340501), for all payroll areas (01 u2013 Workers), during salary processing. During reconciliation, segregation of the information becomes time consuming.
   Analysis:
      The present process needs to be re-visited. If possible, the separate G/L codes to be provided for accounting employeeu2019s claims. This will expedite the reconciliation process.
I.As-Is: Employee claims handling
     1. Employee raises claim in the SAP (LTA/Journals/Driver allowance/Leave encashment/salary advance).
     2. Claim is approved in the system & payment is processed.
     3. The claim related payment/s, for all the payroll areas, gets credited to employeeu2019s account through G/L code u2013 340501.
                                                     Pay Roll Area (01 u2013 Workers)
                     Salary and Wages               -
>                           G/L - 340501
                     LTA                                       -
>                           G/L - 340501
                     Journals                               -
>                           G/L - 340501
                     Driver Allowance                 -
>                           G/L - 340501
II. TO-BE (Business Requirement): Employee claims handling
     1. Employee raises claim in the SAP (LTA/Journals/Driver allowance/Leave encashment/salary advance).
     2. Claim is approved in the system & payment is processed.
     3. The payment related to claim gets credited to G/L code u2013 XXXXXX.
     4. The payment get
                                                     Pay Roll Area (01 u2013 Workers)
                     Salary and Wages               -
>                           G/L - 340501
                     LTA                                       -
>                           G/L - 340502
                     Journals                               -
>                           G/L - 340503
                     Driver Allowance                 -
>                           G/L - 340504
Thanks and best regards
DucTV1

Rge : F110

When we run F110,DME file is generating when we download.
We want in .csv format
Please tell me the configuration or program.
JABEEN

>
mjabeen wrote:
> Program we are using is RFFOES_T.
If you read the documentation of the program the DME file should be downloaded via DME Manager(FDTA).
Anyways fyi the data is written to the TemSe or the file system in the subroutine 'STORE_ON_FILE'(include RFFORI99).
TRANSFER daten TO hlp_filename.
Since payment files are supposed to be secure i would suggest to pass the data in CSV format to DME manager & download it via FDTA.
Hope i'm clear.
BR,
Suhas

Is there any (easy) way to use Pages to edit documents imported via iFiles?

Is there any (easy) way to use Pages to edit documents imported via iFiles?

That is a question better answered by the developer:
http://www.ifilesapp.com/
Peter

DME IFILE format

hi,
Has anyone configured Ifile format for DME?
There is an option for cheque deliver to counter or cheque return/customer pick up.
Could you please let me know how to handle this scenario. Maybe some field has to be populated with this option first and then address allocated?
S Mehta

Hello Shivaz,
This would have to be some custom solution, if you think about the option the bank is providing, send cheque to vendor, or back to office - how are the users going to determine this during a payment run? Will it depend sometimes or will a single vendor always have the same option selected.
If sometimes it will depend, then this option is very difficult to code for - how will person doing payment run indicate per vendor whether cehque is going to vendor or going back to office.
My suggestion is you hard code 1 option in the DME & that is the option that will always be used.
If same vendor will always same option & the customer has vendors that are both send to vendor & send to office, then you need to look at fields available on vendor master record that could be used to indicate this & then you can link DME to this field.
Regards,
Steve

Creation of DME medium FZ205 There is no source data found

We are executing payment runs using F110 and then creating data medium - a file to send to the bank.
In the variant for the program I am putting C:\ however when I have several users executing payment runs at the same time, the data medium is not creating and I am getting the error message that the source data cannot be found
Can anyone help me with this issue - should I leave the file name as blank?
Thanks
Liz

Hello,
In order to avoid FZ205 please review your selection parameters and F1 help for the print program when creating the file:
1. If you are taking the Output to file system:
If required, the file can be written to the file system. The created file can be copied to a PC using data medium exchange management. You should be looking for downloaded files here, since the data carrier is not managed within the SAP system, but is already stored in the file system by the payment medium program. The file name should be defined by the user. You should make sure that existing files with the same name have already been processed, because they will be overwritten.
Note:If a file cannot be found using the data medium exchange management the reason could be that the directory that was written to at the start of the payment medium program (in background processing, for example) cannot be read online.
You should then select a directory which can be recorded and read by several different computers. Due to the problems described above and the resulting lack of data security, we advise against writing to the file system. This method is only beneficial if the data carrier file is taken from the file system by an external program, to be transferred to the bank.
2. If you are taking Output into TemSe:
If required, the file created can be stored within the SAP System(store in the TemSe and not in the file system),thus protecting it from unauthorized external access. You can download the file into the user's file system via the DME manager. The name of the file to be created during the download can be determined when running the payment medium program: the contents of the
file name parameter are stored in the management data and defaulted when running the download.
Please check the corresponding files in the DME administration for all files and check if the output medium 'File-System' has been
chosen, that means output medium '0'. In order to use the TemSe you have to use the output medium '1'. Furthermore see if the PC-file- paths, like c:\filename.DAT, instead of application file names. The FDTA has difficulties to find these files, especially by using 2 application servers.
To avoid problems with the files SAP recommends you to use the TemSe with output medium '1', or the file system with output
medium '0'. TemSe is always a better option.
I hope this helps.
Best regards,
Suresh Jayanthi.

Query regarding the conversion of DME file in MT940 format.

Hello Experts,
I have a query regarding the generation of MT940 file after generating the payment file from other DME tree.
After completion of payment run, my payment file is generated in the DME format which is according to the DME tree.
I want to convert the DME file (which is generated via F110) from existing format to the standard MT940 format.
Is there any standard program which converts the DME file to MT940. If so, please inform me as early.
I have tried to upload the DME file in FF.5 transaction, but it is not allowing me to convert the file in MT940 structure.
Or please inform the steps how i can convert the file .
Awaiting for your inputs.
Thanks in advance

Hi Zareena.
I would like to suggest,
SX_OBJECT_CONVERT_RAW_TXT.
Hope that's usefull.
Good Luck & Regards.
Harsh Dave

HSBC ifile via DMEE

Similar Messages

Maybe you are looking for