cancel
Showing results for 
Search instead for 
Did you mean: 

External bank transfer, prepare data exchange

Former Member
0 Kudos

Hi experts!!

When we make a external transfer, the file is not correct because it looks like a file transfer of the payroll instead of a external transfer.

The format of the file is explained in the "Norma 34".

In the payee line that contains '010', the amount and the bank account, there is a character in position 61 where is indicated 1, 8, 9 and It means:

'1' Nomina (payroll)

'8' Pension

'9' Otros conceptos (another concepts)

When we make an external transfer it should be '9' but always is '1'.

In the report RFFOES_T, in the include RFFORIE3 I have found this code

...

CASE REGUH-LAUFI+5(1).

WHEN 'P'.

MOVE '1' TO DTA_HLP_CONCEPT.

WHEN OTHERS.

MOVE '9' TO DTA_HLP_CONCEPT.

...

Then it seems that the program decide set '1' or '9' from the code of the 'Identification feature'. This identification feature always is set NNNNNP, five number and letter 'P', when we prepare the data exchange.

How is possible set the 'identification feature' different of ending 'P' when we prepare the data exchange?

Kind regards,

Julian

Accepted Solutions (0)

Answers (1)

Answers (1)

antoine_foucault
Active Contributor
0 Kudos

Hola,

Then it seems that the program decide set '1' or '9' from the code of the 'Identification feature'. This identification feature always is set NNNNNP, five number and letter 'P', when we prepare the data exchange.

IN RPCDTAE0 inlcude logic RPCDTM00 P is forced

seth_laufi = save_uzeit.

seth_laufi+5(1) = 'P'. "Identifikationsmerkmal

if not set_laufd is initial. seth_laufd = set_laufd. endif.

if not set_laufi is initial. seth_laufi = set_laufi. endif.

setp_count = 0.

Could you please be keen and elaborates on what is it you trying to do?

Cheers.

Former Member
0 Kudos

Hi Antoine!

At the moment we have three types of transfers:

1-Payment of the payroll (nómina). The flow is from Company to the employ.

2-Garnishments Spain(embargos). The flow is from Company to the Judicial Court in name of the employ.

3-Unions (sindicatos). The flow is from Compay to the Union in name of the employ.

Number (1) at the moment is working right.

Number (2) and (3) we are trying to use.

For the Garnishments (2) we are not using the SAP standar module, we are using the external transfers Infotype 0011

For the Unions (3) we are using the Membership Fees Infotype 0057.

When we try to create the file transfer (norma 34 CBS) the file is not correct for garnishments (2) and Unions (3), because the system generates the file like a payroll payment and this is wrong. It writes a '1' instead of '9'. In the specifications of norma 34 shows that '1' is for payroll payment and '9' for another (garnishments, unions, etc.)

We have tried to use a new payment method specifically for Judicial Withdrawls and another for the Unions, different of the payroll payment.

In the customizing for "Payment Method/Country" (in Tr FBZP), we have filled the field "Key in Code Line" with 09. -> T042Z-TXTSL.

But if we try to use the standar payment process with the new one, the first step when we create the date exchange we get the error:

---

Enter 0 or 1

Message no. ICC-FI461

---

The first step of the transfers process is done always with standar transaction PC00_M04_CDTA - Prepare data exchange.

If we use the payment method 'T' is working for payroll payment.

If we use the payment method 'T' doesn't show error but in the file puts a '1' tha is not correct, it should be '9' to be correct.

If we use the paymen method 'X' (new created for garnishments) the above transaction shows an error ( ICC-FI461).

So we can't create a correct file to transfer the garnishments or Unions fees.

Kind regards,

Julian.

antoine_foucault
Active Contributor
0 Kudos

Hi Julian,

This is very nice. I am guessing from all your questions on SDN you are in a very interesting project and learning a lot. Good for you man.

First of all I want to say from my knowledge that standard CBS for Spain is 34.1 but I know from my last project the FI guys insisted on 34 - we have had countless discussions on it - no payment troubles - however I have not checked on system set up since from HR perspective it is transparent.

Let's discuss first Union fees payment issue:

In my actual assignment, information is also stored in infotype 0057 however payment is not made at HCM level but in FI (after payroll posting).

In my previous project, we did not even bother with infotype 0057 and went for infotype 0011 (both for union fees and donations to a fundation) which was processed in ENN0 subscheme - processing P0011 function with a Z rule that would call the BTREC operation with no further specific customizing. (BTREC operation create an entry in BT table for the WT being evaluated) and P0011 specified bank details. After payroll evaluation, you would go for the PME program (RPCDTAE0) and run the program for specifc wagetype to create the bank transfer file. No problem with P such as you report.

Now for your payment problem:

Make sure with your FI guys which CBS norm should you use. If 34 is fine then:

System message ICC-FI461 occurs because "fils details / detalle del fichero" paremters (PAR_DET) has other value than 0 or 1 when it requires 0 or 1 only. So maybe we can avoid message generation populating this paramters with the correct value - no help associated to it other than code comment "To determine details" but logic effectively describe behavior.

 FORM CAB_ORD_FUELLEN.
* 1. Registro obligatorio:

...
* NUMERO DE LA CUENTA DEL CARGO.
  DTAXESCAB_1-F5 = REGUH-UBKNT(10).

* VALIDATION FOR CHECKING THE LENGTH OF THE INPUT PARAMETER

  PAR_DET_LEN = STRLEN( PAR_DET ).

          IF NOT ( PAR_DET CO '01' AND PAR_DET_LEN EQ 1 ). 
!!!!!! <== if value is other than 0 or 1 then message !!!!! 
                MESSAGE E461(ICC-FI).
        ENDIF.

* DETALLE DEL CARGO
* DTAXESCAB_1-F6 = '0'.
  DTAXESCAB_1-F6 = PAR_DET.
...

I am not sure of why 1 is working VS 2 and 3 since your scenario details alike conditions. My guess is this parameters has different value.

Regards.

Former Member
0 Kudos

Thank you very much!!!