Error while trying to post DEBMAS idoc - Inbound

[Former Member]

Hi All,

I am using a customer master ALE to send idocs from one R/3 system to another. The message type used is DEBMAS. All ALE settings are completed in both inbound and outbound side. The idoc is sent successfully from the sender system.

I am encountering couple of errors in the Inbound side when I try to process the debmas idoc -

1) "PO Box postal code must have length 05"

2) "Personal master record ####### does not exist.

I can avoid the first error by changing the postal code for 5 char; however in the sender it has been maintained as 123 45 (for example) ie with a space. Please advise if there is any customization I can do in the receiver system such that the change of postal code is flexible. Is this advisable?

For the second one, I am unsure what is the conenction between customer record and a personal master record (i assume this is the HR personnel # ). Please advise.

TIA!

Rds, Liz

[Former Member]

Hi All,

I am using a customer master ALE to send idocs from one R/3 system to another. The message type used is DEBMAS. All ALE settings are completed in both inbound and outbound side. The idoc is sent successfully from the sender system.

I am encountering couple of errors in the Inbound side when I try to process the debmas idoc -

1) "PO Box postal code must have length 05"

2) "Personal master record ####### does not exist.

I can avoid the first error by changing the postal code for 5 char; however in the sender it has been maintained as 123 45 (for example) ie with a space. Please advise if there is any customization I can do in the receiver system such that the change of postal code is flexible. Is this advisable?

For the second one, I am unsure what is the conenction between customer record and a personal master record (i assume this is the HR personnel # ). Please advise.

TIA!

Rds, Liz

[Former Member]

second error is related to HR personnel master record, please get in touch with your HR functional consultant and get the record maintained on reciever side

[JL23]

your first error is caused by different customizing in your 2 systems.

IMG > SAP NetWeaver > Set Countries > Set Country-Specific Checks

Have a look at the postal code length and checking rule .

[Former Member]

Thanks! Changing the postal code length did the trick!!

Liz