Skip to main content
Solved

C18 Posting Error for Shipment Charges on Shipment Invoice

  • April 28, 2025
  • 4 replies
  • 72 views
E
Sidekick (Partner)
Forum|alt.badge.img+9

Hi,

I am facing posting error on Shipment Charges in Shipment Invoice for Posting Type M68, M69, M70 Control Type C18 for Code Part F. I have attached the document for the detail setup i have done. I found the same issue in Apps-9 and Cloud as well. Can someone help me on this?

 

Regards-

Nahin

Best answer by Pilar Franco

Thanks, ​@EntNananN ,

I found some old solutions with this problem and it was due to the charges not connected to any customer order line or the use of Single Occurrence address in it.

“This control type always use the value from the CO line. However in the case when the charge is not connected to any CO line, the system will fail to find a value. It works fine if e.g. using a control type that retrieves the value from the CO header, e.g. C19.
Further correction must be made for the case when a charge is not connected to any CO line, to retrieve the values from the CO header. If the charge line is connected to a CO line, the values should be retrieved as now.
Currently there is no workaround to the problem other than to connect the charge to a CO line, but this can not be seen as an acceptable workaround.”

A bug fix was provided for both problems, so then I suggest you to create a support case for IFS Cloud product (recommended with a test case in a Reference environment), so it can be investigated by Support team.

Regards,

Pilar

1 Attachments

4 replies

P
Superhero (Employee)
Forum|alt.badge.img+17
  • Pilar Franco
  • Superhero (Employee)
  • April 28, 2025

Hi ​@EntNananN ,

I checked your document but I still need more clarification about the Code Part F definition.

Also, as far as I can see in the screenshots, the Posting Control details have been defined in your company ‘ENTERPRISE ANALYTICS’, but the posting error is shown related to company N-01, that it’s shown in your site definition as ‘Test Company’.

Please, confirm if the posting control definition corresponds to the same company of your shipment and order.

Regards,

Pilar

E
Sidekick (Partner)
Forum|alt.badge.img+9
  • EntNananN
  • Author
  • Sidekick (Partner)
  • April 28, 2025

Hi ​@Pilar Franco ,

It was a wrong screenshot but I had the same setup in Test company as well. See below screenshot:

 

Regards-

Nahin

P
Superhero (Employee)
Forum|alt.badge.img+17
  • Pilar Franco
  • Superhero (Employee)
  • Answer
  • April 29, 2025

Thanks, ​@EntNananN ,

I found some old solutions with this problem and it was due to the charges not connected to any customer order line or the use of Single Occurrence address in it.

“This control type always use the value from the CO line. However in the case when the charge is not connected to any CO line, the system will fail to find a value. It works fine if e.g. using a control type that retrieves the value from the CO header, e.g. C19.
Further correction must be made for the case when a charge is not connected to any CO line, to retrieve the values from the CO header. If the charge line is connected to a CO line, the values should be retrieved as now.
Currently there is no workaround to the problem other than to connect the charge to a CO line, but this can not be seen as an acceptable workaround.”

A bug fix was provided for both problems, so then I suggest you to create a support case for IFS Cloud product (recommended with a test case in a Reference environment), so it can be investigated by Support team.

Regards,

Pilar

E
Sidekick (Partner)
Forum|alt.badge.img+9
  • EntNananN
  • Author
  • Sidekick (Partner)
  • April 29, 2025

Hi ​@Pilar Franco ,

I could not beleive this bug is carried from Apps-9 till the latest version of Clouds like 24R1. That why i thought to check if I was missing anything or not.

But thanks for the help.

Regards-

Nahin

Terms & ConditionsCookie settingsAccessibility statement