how to re push the SAE file in case of failure

[paramjeet]

How to re push the SAE file in case of failure... is there any way we can do that... and also can we limit the no. of line items created because of attendees, allocation, tax etc as ECC has a limit of 599 line items per claim

[PoojaKumatkar]

Hi @paramjeet ,

May I know which Integration method you are currently using? SFTP flat file Or ICS integration? 

In SFTP setup, it is feasible to re-push SAE.

In ICS integration, since there is  direct connection between SAP and Concur, technically you can re-push the same report by using "recall to processor" button which is available in processor screen, do the necessary changes in the report and approve it from processor. Once approved it should get posted into SAP. In ICS integration there is no concept of SAE file. 

Regarding number of lines restriction, as per my understanding there is no such restriction on number of lines in Concur application. However, if report contains 50/60+ line items, then I would suggest you to try dividing one of such report into 2-3 reports and test whether it get posted successfully. For one of our client we did the same thing and it worked.

If issue still persists then I would suggest raising a support ticket with Concur.

If this answers your query, then please mark solution as accepted.

[paramjeet]

No i am not talking about one report, its when the all the claims are interfaced from concur to SAP and then the entire SAE is failed, we dont have any option to rerun the entire SAE file or modify it... and also we need to remove the claim which is creating problem and then rerun the file with the remaining ones.. The claims are interfaced once in a day from concur to SAP.

In SFTP setup, it is feasible to re-push SAE - Could you pls explain the process 

and also we are talking about limitation in SAP ECC and not in concur.

[PoojaKumatkar]

Hi @paramjeet ,

Please find my response below:

SFTP Flat file Integration Extract:

• If you are using SFTP flat file integration method then technically it is feasible to re-push entire SAE file with the help of Import/Extract Administrator Access.
• Role Required - Expense Configuration Administrator (Unrestricted)
• Note - Only with unrestricted access, you will get Import/Extract Administrator role by default.
• To re-run SAE follow below navigations: 

Note - When using SFTP flat file integration, when you re-run SAE, entire SAE file will be re-pushed to ERP. To exclude any specific reports from the SAE, technically it is feasible to modify extract configuration definition based on testing requirement, however, this is restricted configuration item and available ONLY for the Concur and users who have unrestricted configuration access and have required knowledge to modify the same. 

• 

ICS Integration Extract - SAP ECC :

As per my understanding when using ICS integration it is not feasible to re-push extract file and exclude specific reports which is causing issue. 

@KevinD- Can you please confirm on this point.

If this answers your query then please mark solution as accepted. 

[KevinD]

@PoojaKumatkar and @paramjeet unfortunately ICS isn't my area of expertise. I'm strictly SAP Concur products. However, maybe my colleague @Andras can provide some information as he works with ICS. 

[Andras]

Hi everyone, @paramjeet @PoojaKumatkar @KevinD 

If you're encountering issues with failed SAE files in SAP Concur, here's some guidance that might help:

1. Integration Details:

   • It's possible for SAE files and ICS integration to operate simultaneously under specific configurations. For instance, reports might be processed via ICS for financial integrations and managed through SAE files when financial integration isn't enabled.
   • However, running both integration types simultaneously may lead to complexities, similar to conflicts with concurrent use of Employee Import and Employee Replication.

2. Re-pushing SAE Files:

   • If you need to re-run the SAE file due to failure, the process isn't directly accessible to clients. You'll need to contact your Service Coordinator or the SAP Concur Support team to request a rerun. Provide them with details such as the job name, run number, output file name, and file name.
   • There isn't a feedback mechanism for SAE files post-extraction similar to ICS, limiting the ability to track or adjust once the file is processed.

Managing these integrations often requires support for reruns and troubleshooting to address problematic reports. If anyone has additional experiences or solutions, please share!