on 2018 Jan 10 9:55 PM
1. Saludos a todos,
Espero que alguien me pueda ayudar con la siguiente cuestión de la reclamación: después de ejecutar la transacción FPVA, algunas facturas vencidas no tenían nivel de reclamación, por lo que realizar las siguientes actividades:
- Verificar el registro de la aplicación (FPVA), no mostrar los mensajes de error, pero si los mensajes informativos (3226 Constituido (s) 1 grupo (s) de reclamación y 3229 El nivel de reclamación no se ha aumentado para ningún elemento, entre otros),
- Revisar los datos maestros de los diferentes socios comerciales con nivel de reclamo y sin nivel de reclamo para detectar diferencias,
- Revisar datos de un socio comercial, con el mismo contrato de cuenta con diferentes tipos de documento (DR / FA) con y sin nivel de reclamación,
- La depuración del informe "Z",
In the end, I could not detect the origin or reason why some overdue invoices appear without claim level after executing the process to assign it. Thanks in advance, I look forward to your comments on this.
regards DMDL
Request clarification before answering.
Hi!!
- The documents are expired for several days, for this reason should be assigned a level of claim or the last of the levels, but does not show anything
- I understand that there are no limits $ (As I can verify the configuration) the process is generated without considering the amount, only days of expiration.
The configuration was one of the first points reviewed; I will appreciate the recommendations in this regard.
regards
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I explain the problem again: Execute the transaction FPVA - Proposed claim, when I visualized the report I realized that some expired documents are not assigned level of claim, so I carry out the following activities:
- Check application logs (FPVA), which shows several informative messages between them: 3-226 Constituted (s) 1 group (s) of claim and 3-229 The level of claim has not been increased for any element, among others . (Log-4 applies) - Review the master data of the different business partners that presented documents with a claim level and without a claim level to detect possible differences that could affect the claim level assignment,
- Review data of a business partner, with the same account agreement with different types of document (DR / FA) with and without level of claim,
- Modify the ranges of application of the transaction: from 1 to 999 ... and from A to ZZZ
- The amount limit is verified, it is: $ 0.00
- The "Z" report was debugged,
In spite of the above, it does not detect the origin or why some expired documents are left without a level of claim. Thanks in advance and I look forward to your comments.
Greetings.
if message >3 229 is issued then that indicates that the item(s) have not moved to the next level. Possibly they are below $ threshold, or the days in arrears, or the frequency have not been met. You need to check your configuration.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Good morning William!
The transaction is always executed with that option, just to detect errors; The revised business partners only display informational messages: 3-226: Constituted 1 group (s) of claim
3-229: The claim level for any item has not been increased
As far as I review and understand, none of these messages is limiting for the claim level assignment; One of the reviewed cases shows the same messages and the expired documents have the corresponding level of claim. I tell you that all claim levels executed show only informative messages.
After seeing that the informative messages do not originate, start the search on the internet, but still can not find anything.
I appreciate your comments.
regards
DMDL
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Make sure that you have set the log level to 4 - Additional information. Then the application log will provide details about the reason for failure to dun successfully.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
79 | |
22 | |
9 | |
7 | |
6 | |
5 | |
4 | |
4 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.