cancel
Showing results for 
Search instead for 
Did you mean: 

US AES Aggregation Understanding

dean_hinson2
Active Contributor
0 Kudos

Hello,

My customer believes that the aggregation that is done on the printed SLI form is the same aggregation that should be sent to US AES (ACE).

I find that we have configured the Aggregation Schema CUSE1.When I reviewed the code in FM /SAPSLL/LCUHD_AGGREGATIONF14, the aggregation seems to be more than that on the SLI and complicated.

I couldn't find any documentation on the Aggregation being done. Do anyone have information on this Aggregation for US AES?

I need to explain to my customer.

Thank you in advance.

Regards, Dean.

Accepted Solutions (1)

Accepted Solutions (1)

former_member215181
Active Contributor
0 Kudos

Hi Dean,

In addition to the "visible" aggregation criteria that you can see listed in the Declaration, there are lots more - some obvious, some less so. In the code, I can see these fields for CUSE1:

  • External Item Number
  • Item Category
  • Source and Destination Procedures
  • Item Status fields (ITSTA, STICF, STICC)
  • Legal Unit
  • Product Unit of Measure
  • Weight Unit of Measure
  • Volume Unit of Measure
  • Customs ID (ECPID)
  • OPR Customs ID
  • Additional Stock ID
  • Preference Indicator
  • Supplementary Declaration indicator
  • Duty Types
  • Item Currency
  • Exchange Rate indicators
  • Exchange Rate types
  • Percentage operators
  • Package Types and numbers
  • Licence Type
  • Licence Unit of Measure
  • Licence Currency
  • Country of Origin
  • Range of Goods
  • Supplementary Units of Measure
  • Ship-to Party
  • Ultimate Consignee
  • Item Documents (all fields)
  • Goods Description

I hope that's enough information for you. I can't comment on the aggregation carried out for the printed form - at least not today (it's too tiring!)

Regards,
Dave

dean_hinson2
Active Contributor
0 Kudos

Hello Dave,

Yep, the analyzing the code would definitely result in a serious migraine. I just thought there might be some documentation hidden somewhere where I had not looked.

When my customer looked at the 601 file that is sent to ACE, the L13 is repeated for the same Schedule-B. But now as I look the product description is different for the products with the same classification. So, per your information, the good description will cause separate aggregation. This we do not do on our SLI form.

So, I will have to discuss with customer and hopefully I will not be asked to open an OSS Message with SAP.

Thanks you your continuing support to the GTS Community.

Regards, Dean.

dean_hinson2
Active Contributor
0 Kudos

Hello Dave,

Found something where I needed to open an OSS Message to SAP. If you have the line item aggregation checked in the IMG, the data that was modified @ line item level via MODIFY_IDOC_VIEW is discarded and recollected in order to do the aggregation.

For those that use MODIFY_IDOC_VIEW to implement the under $2,500 no filing for US Exports, this is a big issue.

I will keep you posted with how SAP responds.

Regards, Dean.

Answers (0)