Error sheet processing method and device, equipment and medium

Abstract

The invention relates to the technical field of data processing, in particular to an error list processing method and device, equipment and a medium, and is used for solving the problems of low processing efficiency and low accuracy caused by manual error list processing. The method comprises the following steps: acquiring a plurality of target details generated in a set date from an accounting engine component, and acquiring an error list generated before the set date from each bookkeeping component; wherein the target details are the details which are the same as the to-be-leveled detail identification and are successful in consistency checking, the to-be-leveled detail identification is the identification of the details which are failed in transaction consistency checking before the set date, and the error list comprises a plurality of error details; comparing the identifiers of the plurality of target details with the identifiers of the error details in the error orders, and determining at least one target error order from the error orders according to a comparison result; and for each target error list, processing each target error list based on the obtained multiple target details.

Description

Technical Field

[0001] The present application relates to the field of data processing technology, and in particular to an error ticket processing method, device, equipment and medium. Background Art

[0002] The same business will be recorded in multiple accounting components, and then the accounting information will be summarized for day-end verification. Due to the inconsistency of daily cut-off time and data supply time of different components, the accounting data may be divided into different day-end batches for verification (for example, the same business data may be distributed in the T-day batch and the T+1 day batch). For a single day-end batch, the account of this business is incomplete, which will cause uneven accounts, that is, false uneven details, and then generate error orders. There are a large number of false uneven details in the cross-system uneven account error orders, which need to be manually identified and processed, with low processing efficiency and difficulty in ensuring processing accuracy. Summary of the invention

[0003] The embodiments of the present application provide an error ticket processing method, device, equipment and medium, which are used to solve the problems of low processing efficiency and low accuracy caused by manual processing of error tickets.

[0004] In a first aspect, an embodiment of the present application provides a method for processing an error ticket, the method comprising:

[0005] Acquire multiple target details generated on a set date from the accounting engine component, and acquire error slips generated before the set date from each accounting component; wherein the target details are details that have the same identifier as the details to be settled and have successfully undergone consistency check, the details to be settled are identifiers of details that have failed transaction consistency check before the set date, and the error slips include multiple error details;

[0006] Comparing the identifiers of the multiple target details with the identifiers of the error details in the error sheet, and determining at least one target error sheet from the error sheet according to the comparison result;

[0007] For each target error sheet, each target error sheet is processed based on obtaining the multiple target details.

[0008] Based on the above scheme, the present application obtains the target details of the set date, and determines at least one target error sheet among the error sheets generated before the set date through the identification of the target details, and then processes each target error sheet based on multiple target details. It can automatically identify the error sheets, and then realize automatic processing of error sheets, thereby improving the processing efficiency of error sheets and having high accuracy.

[0009] In a possible implementation, the processing of each target error ticket based on obtaining the multiple target details includes:

[0010] Determine the total number of error details in each target error list and the target number of error details corresponding to each target error list, wherein the target number of error details is the number of error details in the target error list having the same identifier as the target detail;

[0011] Matching the total number of error details with the target number of error details;

[0012] The target error ticket is processed based on the matching result.

[0013] Based on the above scheme, the present application counts the total number of error details and the target number of error details in the target error list, matches the total number with the target number of error details, and then processes the target error list in different ways based on the matching results.

[0014] In a possible implementation, the processing of the target error ticket based on the matching result includes:

[0015] If the matching result is that the total number of the error details is equal to the target error detail number, the status of each error detail in the target error sheet is changed to a processed status, and the target error sheet is closed;

[0016] If the matching result is that the total number of the error details is greater than the target number of error details, the target error list is modified based on the multiple target details.

[0017] Through the above scheme, when the total number of error details is equal to the target number of small error details, you can directly choose to close the order. When the total number of error details is not equal to the target number of error details, you can modify the target error details.

[0018] In a possible implementation, the modifying the target error sheet based on the multiple target details includes:

[0019] According to the identifiers respectively corresponding to the multiple target details, determine N target error details in the target error list having the same identifier as the target detail, where N is a positive integer;

[0020] Creating a new error sheet based on the error details in the target error sheet except the N target error details, and closing the target error sheet;

[0021] The status of each error detail in the new error sheet is set to a pending status.

[0022] Based on the above scheme, the present application can establish a new error ticket through error details other than the target error details, that is, establish a new error ticket through the details that failed the consistency check, and then realize the processing of the error ticket.

[0023] In a possible implementation, the processing of the target error sheet based on the multiple target details includes:

[0024] According to the identifiers respectively corresponding to the multiple target details, determine N target error details in the target error list having the same identifier as the target detail, where N is a positive integer;

[0025] The status of N target error details in the target error list is modified to a processed status, and a new target error detail quantity is determined based on at least one error detail in a pending status in the error list.

[0026] Based on the above scheme, the present application can modify the status of the target error details, thereby realizing the processing of the target error details in the error sheet.

[0027] In a possible implementation, comparing the identifiers of the multiple target details with the identifiers of the error details in the error sheet includes:

[0028] Determine M error details in the error list whose error detail status is in a pending state, where M is a positive integer;

[0029] For any one of the M error details, the identifier of the any one error detail is compared with the identifiers of the multiple target details.

[0030] Based on the above scheme, before performing the comparison, this application needs to determine the status of the error details in the error list, and then compare the identification of the error details that need to be processed with the identification of the target details, which can save comparison time and improve processing efficiency.

[0031] In a possible implementation, determining at least one target error ticket from the error tickets according to the comparison result includes:

[0032] For each error ticket, when the comparison result is that the identifier of at least one error detail included in the error ticket is the same as the identifier of the target detail, the error ticket is used as the target error ticket.

[0033] In a second aspect, the present application provides an error ticket processing device, the device comprising:

[0034] An acquisition module, used to acquire multiple target details generated on a set date from the accounting engine component, and to acquire error slips generated before the set date from each accounting component; wherein the target details are details that have the same identifier as the details to be settled and have successfully undergone consistency check, the details to be settled are identifiers of details that have failed transaction consistency check before the set date, and the error slips include multiple error details;

[0035] A processing module is used to compare the identifiers of the multiple target details with the identifiers of the error details in the error sheet, and determine at least one target error sheet from the error sheets according to the comparison result; for each target error sheet, process each target error sheet based on obtaining the multiple target details.

[0036] In a possible implementation, the processing module, when processing each target error sheet based on obtaining the multiple target details, is specifically configured to:

[0037] Determine the total number of error details in each target error list and the target number of error details corresponding to each target error list, wherein the target number of error details is the number of error details in the target error list having the same identifier as the target detail;

[0038] Matching the total number of error details with the target number of error details;

[0039] The target error ticket is processed based on the matching result.

[0040] In a possible implementation, when processing the target error ticket based on the matching result, the processing module is specifically configured to:

[0041] If the matching result is that the total number of the error details is equal to the target error detail number, the status of each error detail in the target error sheet is changed to a processed status, and the target error sheet is closed;

[0042] If the matching result is that the total number of the error details is greater than the target number of error details, the target error list is modified based on the multiple target details.

[0043] In a possible implementation, when modifying the target error sheet based on the multiple target details, the processing module is specifically configured to:

[0044] According to the identifiers respectively corresponding to the multiple target details, determine N target error details in the target error list having the same identifier as the target detail, where N is a positive integer;

[0045] Creating a new error sheet based on the error details in the target error sheet except the N target error details, and closing the target error sheet;

[0046] The status of each error detail in the new error sheet is set to a pending status.

[0047] In a possible implementation, when modifying the target error sheet based on the multiple target details, the processing module is specifically configured to:

[0048] According to the identifiers respectively corresponding to the multiple target details, determine N target error details in the target error list having the same identifier as the target detail, where N is a positive integer;

[0049] The status of N target error details in the target error list is modified to a processed status, and a new target error detail quantity is determined based on at least one error detail in a pending status in the error list.

[0050] In a possible implementation, when comparing the identifiers of the multiple target details with the identifiers of the error details in the error sheet, the processing module is specifically configured to:

[0051] Determine M error details in the error list whose error detail status is in a pending state, where M is a positive integer;

[0052] For any one of the M error details, the identifier of the any one error detail is compared with the identifiers of the multiple target details.

[0053] In a possible implementation, when determining at least one target error ticket from the error tickets according to the comparison result, the processing module is specifically configured to:

[0054] For each error ticket, when the comparison result is that the identifier of at least one error detail included in the error ticket is the same as the identifier of the target detail, the error ticket is used as the target error ticket.

[0055] In a third aspect, the present application provides an electronic device, including:

[0056] A memory for storing program instructions;

[0057] The processor is used to call the program instructions stored in the memory, and execute the steps included in any one of the methods in the first aspect according to the obtained program instructions.

[0058] In a fourth aspect, the present application provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, wherein the computer program includes program instructions, and when the program instructions are executed by a computer, the computer executes any one of the methods described in the first aspect.

[0059] In a fifth aspect, the present application provides a computer program product, comprising: a computer program code, when the computer program code is run on a computer, the computer executes any one of the methods described in the first aspect.

[0060] In addition, the technical effects brought about by any implementation method of the second to fifth aspects can refer to the technical effects brought about by the first aspect and different implementation methods of the first aspect, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0061] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative labor.

[0062] Figure 1 A flowchart of a method for processing an error ticket provided in an embodiment of the present application;

[0063] Figure 2 A schematic diagram of a method for modifying an error ticket provided in an embodiment of the present application;

[0064] Figure 3 A schematic diagram of another error ticket modification method provided in an embodiment of the present application;

[0065] Figure 4 A flowchart of error ticket processing provided in an embodiment of the present application;

[0066] Figure 5 A schematic diagram of an error ticket processing device provided in an embodiment of the present application;

[0067] Figure 6 A structural diagram of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0068] In order to make the purpose, technical scheme and advantages of the present application clearer, the technical scheme in the embodiment of the present application will be clearly and completely described below in conjunction with the drawings in the embodiment of the present application. Obviously, the described embodiment is only a part of the embodiment of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in the field without making creative work are within the scope of protection of the present application. In the absence of conflict, the embodiments in the present application and the features in the embodiments can be arbitrarily combined with each other. In addition, although the logical order is shown in the flow chart, in some cases, the steps shown or described can be performed in an order different from that here.

[0069] The terms "first" and "second" in the specification and claims of the present application and the above-mentioned drawings are used to distinguish different objects, rather than to describe a specific order. In addition, the term "comprising" and any of their variations are intended to cover non-exclusive protection. For example, a process, method, system, product or device comprising a series of steps or units is not limited to the listed steps or units, but optionally also includes steps or units that are not listed, or optionally also includes other steps or units inherent to these processes, methods, products or devices. "Multiple" in the present application can mean at least two, for example, two, three or more, and the embodiments of the present application are not limited.

[0070] The following is a description of exemplary embodiments of the present application in conjunction with the accompanying drawings, including various details of the embodiments of the present application to facilitate understanding, which should be considered as merely exemplary. Therefore, those of ordinary skill in the art should recognize that various changes and modifications can be made to the embodiments described herein without departing from the scope of the present application. Similarly, for the sake of clarity and conciseness, the description of well-known functions and structures is omitted in the following description. It should be noted that in the embodiments of the present application, certain software, components, models and other existing solutions in the industry may be mentioned, which should be considered as exemplary, and their purpose is only to illustrate the feasibility of the implementation of the technical solution of the present application, but it does not mean that the applicant has or will necessarily use the solution.

[0071] In the technical solution of this application, the acquisition, transmission, storage, and use of data are in compliance with the requirements of relevant national laws and regulations.

[0072] In order to better understand the error ticket processing method proposed in this application, the technical terms involved in this application are explained below.

[0073] Consistency check: When one or a group of processes with business consistency requirements are implemented in multiple applications or application components, after the group of processes is completed, a certain method is used to check whether the group of processes has been successfully executed together.

[0074] Error details: data that causes errors during the transaction due to non-compliance with transaction inconsistencies, such as inconsistent data such as imbalanced debits and credits, and imbalanced totals.

[0075] Error sheet: For accounting data that does not meet transaction consistency and has errors, a collection of erroneous account data is classified and a processing sheet is established, which is usually called an error sheet.

[0076] Create an order: Receive and process error details, and assign the error handling order to the primary responsible component by automatically creating an order through system batch processing or manually creating an order at the order processing service post.

[0077] Uneven cross-system transactions: Due to system design defects, technical failures such as downtime, and manual operation errors, some components failed to record accounts successfully, while other components under the same transaction recorded accounts successfully, resulting in the inability to completely offset the accounting items of the transaction, resulting in a unilateral accounting situation.

[0078] False imbalance in cross-system transactions: The same business is recorded in multiple accounting components and finally summarized in the accounting engine accounting system for day-end reconciliation. Due to inconsistent daily cut-off times and data supply times of different components, the accounting data may be divided into different batches of the accounting engine day-end batch for reconciliation (data is distributed in T day batch and T+1 day batch). For a single day-end batch, the accounts of this business are incomplete, which will cause imbalance in accounts. However, if the data of multiple day-end batches are viewed together, the accounts of this business are complete and balanced, so this type of account imbalance is called false imbalance.

[0079] Before introducing the error ticket processing method provided in the embodiment of the present application, in order to facilitate understanding, the technical background of the embodiment of the present application is first introduced in detail below.

[0080] The same business will be recorded in multiple accounting components, and then the accounting information will be summarized for day-end verification. Due to the inconsistency of daily cut-off time and data supply time of different components, the accounting data may be divided into different day-end batches for verification (for example, the same business data may be distributed in the T-day batch and the T+1 day batch). For a single day-end batch, the account of this business is incomplete, which will cause uneven accounts, that is, false uneven details, and then generate error orders. There are a large number of false uneven details in the cross-system uneven account error orders, which need to be manually identified and processed, with low processing efficiency and difficulty in ensuring processing accuracy.

[0081] In response to the above problems, the embodiments of the present application provide a method, device and equipment for processing error orders, which obtain multiple target details generated on a set date from the accounting engine component, and obtain error orders generated before the set date from each accounting component; and compare the identifiers of the multiple target details with the identifiers of the error details in the error order, and determine at least one target error order from the error order based on the comparison results, and then process each target error order. Among them, the processing method includes closing the order or splitting the order, and the specific processing method is determined based on the comparison result of the number of target error details in the target error order and the total number of error details in the target error order. Through the above method, error orders can be automatically identified, and then automatic processing of error orders can be realized, which improves the processing efficiency of error orders with high accuracy.

[0082] The present application embodiment provides a method for processing an error ticket, see Figure 1 As shown, the specific process of this method is as follows:

[0083] Step S101, obtaining multiple target details generated on a set date from the accounting engine component, and obtaining error tickets generated before the set date from each accounting component.

[0084] Among them, the target details are the details that have the same ID as the details to be settled and have been successfully checked for consistency. The details to be settled are identified as the details that failed the transaction consistency check before the set date. The error sheet includes multiple error details.

[0085] In some embodiments, since the transaction corresponding to the same identifier may be accounted by multiple accounting components, and the daily cut-off time of different accounting components is different, it may cause some of the multiple accounting components to successfully account on the day the transaction is initiated, while other accounting components are only successfully accounted on the second day of the day the transaction is initiated. On the day of the transaction, since the other part of the accounting components did not successfully account, the transaction consistency check failed, and then an error sheet was established based on the transaction details of the first responsible component that failed the transaction consistency check. In some scenarios, after another part of the accounting components successfully accounted on the second day of the day the transaction was initiated, the details generated by the other part of the accounting components failed to check the consistency with the details generated by the current part of the components when the transaction was initiated. In this application, the details generated on the day the transaction was initiated are called the details to be settled, and the target details are the details generated on the second day of the current transaction initiation. In some embodiments, when the details of multiple accounting components correspond to the same identifier, the multiple details can be screened and deduplicated, and the same identifier corresponds to one detail. Specifically, the details generated by the accounting component with the earliest accounting time can be selected according to the accounting time, or the details of the accounting component with the earliest transaction can be selected according to the transaction rules.

[0086] In some embodiments, the detail identifier may be a set number or a serial number.

[0087] Step S102, comparing the identifiers of multiple target details with the identifiers of error details in the error sheet, and determining at least one target error sheet from the error sheets according to the comparison result.

[0088] In some embodiments, M error details in the error sheet whose error detail status is in a pending state can be determined, and for any one of the M error details, the identifier of any error detail is compared with the identifiers of multiple target details. Wherein, M is a positive integer. As an example, any error sheet includes S error details, of which there are M error details in a pending state and SM error details in a processed state. Then the identifier of each error detail in the M error details is compared with the identifiers of multiple target details.

[0089] Furthermore, for each error sheet, when the comparison result is that the identifier of at least one error detail included in the error sheet is the same as the identifier of the target detail, the error sheet is used as the target error sheet. The error details are error details in a pending state. As an example, if the identifier of at least one error detail included in an error sheet is the same as the identifier of the target detail, the error sheet is used as the target error sheet. For example, the identifier of error detail A1 in the error sheet is L1, the identifier of error detail A2 is L2, the identifier of target detail C1 is L1, and the identifier of target detail C2 is L2. If the identifiers of error details A1 and A2 in the error sheet are the same as the identifiers of target details C1 and C2, respectively, the error sheet is used as the target error sheet.

[0090] Step S103: for each target error sheet, each target error sheet is processed based on obtaining multiple target details.

[0091] In some embodiments, processing each target error ticket based on obtaining multiple target details can be implemented in the following ways:

[0092] Determine the total number of error details in each target error sheet and the target number of error details corresponding to each target error sheet, wherein the target number of error details is the number of error details in the target error sheet that have the same identifier as the target detail. Further, match the total number of error details with the target number of error details; and then process the target error sheet based on the matching result.

[0093] In some embodiments, processing the target error ticket based on the matching result can be achieved in the following ways:

[0094] In some scenarios, if the matching result is that the total number of error details is equal to the target number of error details, the status of each error detail in the target error form is changed to processed, and the target error form is closed. For example, if the total number of error details in the target error form is 10 and the target number of error details is 10, it is confirmed that each error detail in the target error form has been successfully checked for consistency, so the status of each error detail can be changed to processed, and the target error form can be closed.

[0095] In other scenarios, if the matching result is that the total number of error details is greater than the target number of error details, the target error sheet is modified based on multiple target details. As an example, if the total number of error details in the target error sheet is 10 and the target number of error details is 6, then it can be determined in S403 that 6 error details in the target error sheet have passed the consistency check and 4 error details have failed the consistency check, and the target error sheet needs to be modified based on multiple target details.

[0096] In some embodiments, modifying the target error sheet based on multiple target details can be achieved in the following two ways:

[0097] In the first implementation, N target error details with the same identification as the target details in the target error sheet can be determined according to the identifications corresponding to the multiple target details. Where N is a positive integer. Further, a new error sheet can be created based on the error details other than the N target error details in the target error sheet, and the target error sheet can be closed. Further, the status of each error detail in the new error sheet is set to a pending status.

[0098] As an example, Figure 2 As shown, the target error sheet 1 includes 10 error details, namely error details 1-10, and their corresponding identifiers are K1-K10. Among the target details, 6 target details are identified as K1, K2, K4, K5, K7, and K8. Therefore, a new error sheet 2 can be created based on error details 3, 6, 9, and 10, and the target error sheet 1 can be closed.

[0099] In a second implementation, N target error details with the same identification as the target detail in the target error list can be determined according to the identifications corresponding to the multiple target details, where N is a positive integer. Further, the status of the N target error details in the target error list can be modified to a processed status, and the number of new target error details can be determined based on at least one error detail in a pending status in the error list.

[0100] As an example, Figure 3As shown, the target error list 1 includes 10 error details, namely error details 1-10, whose corresponding identifiers are K1-K10, and whose statuses are pending. Among the target details, 6 target details are identified as K1, K2, K4, K5, K7, and K8, respectively. Then, the status of error details 1, 2, 4, 5, 7, and 8 in the target error list 1 can be modified to the processed status, and the status of error details 3, 6, 9, and 10 is still pending. Furthermore, the number of new target error details of the target error list 1 is 4.

[0101] The following is a detailed description of the error sheet processing method of the present application by way of example. Taking the setting date as T+1 day, the target details (hereinafter referred to as false uneven details) as the details generated on T+1 day, and the error sheets generated before the setting date as the error sheets generated on T+1 day and the error sheets generated on T day as an example, the error sheet processing method is described in detail, see Figure 4 :

[0102] S401, obtain T+1 day target details, T day error list and T+1 day error list.

[0103] Among them, the error order on T day refers to the data generated on T day that failed the consistency check of cross-system transactions, and the error handling order created by the system's automatic order creation process. The error order on T+1 day refers to the data generated on T+1 day that failed the consistency check of cross-system transactions, and the error handling order created by the accounting system's automatic order creation process.

[0104] The error ticket creation process is divided into two cases: one is to create a ticket according to the account balance set number dimension, and the other is to create a ticket according to the global event tracking number (serial number). The specific process is as follows: First, extract the detailed data from the source table to the intermediate table 1, which can be sorted according to the fields such as multi-entity identifier + accounting account balance set number to determine the candidate master record. The source table is used to record the detailed data generated by each accounting component, and the multi-entity identifier is used to indicate the transaction attribute of the detailed data, such as domestic or foreign. Next, determine the primary key of each candidate master record of the set number or serial number, and the record corresponding to the smallest transaction service code of the smallest transaction sequence number can be used as the candidate master record. For example, there are multiple accounting components corresponding to the same set number, and each accounting component has a transaction sequence number according to the transaction order, and each accounting component may have multiple transaction service codes for the same set number. Therefore, the record of the first transaction (that is, the earliest transaction record generated by the component with the smallest transaction sequence number) is selected as the candidate master record. In some scenarios, since the intermediate table 1 has been sorted when it is obtained, it is sufficient to take the smallest primary key of each set number or serial number of the record. The transaction service code of the candidate master record is used as the main transaction service code to obtain the intermediate table 2. Then, the intermediate table 2 is written into the main table EH_FORM_INFO. Finally, the groups with the same main transaction service number will be merged to create another error handling form.

[0105] The unbalanced details on T+1 day are the target details provided by the accounting engine system on T+1 day. The target details are the details with the same ID as the details to be balanced and the consistency check has been successful. The ID of the details to be balanced is the ID of the details that failed the consistency check of transactions before T+1 day.

[0106] S402, determine the target error list based on the false imbalance details and obtain the false imbalance error processing information table.

[0107] Specifically, all relevant target error orders can be queried according to the balance set number (i.e., set number) or serial number in the false unbalanced details (CMPT_FALSE_UNEQUAL), and written into the false unbalanced error processing order information table (AC_FUE_ERR_FORM). When querying the relevant target error orders, it is necessary to determine that the status of the balance set number or serial number is pending, and the error order is an unclosed order (which can be understood as unprocessed) error order.

[0108] After determining the target error sheet, create an error processing sheet information table: the primary key, type (old sheet, new sheet) and status of the error sheet involved. The status is used to indicate whether the error sheet is processed.

[0109] Based on the balance set number or serial number in the false imbalance details, compare it with the balance set number or serial number of the error details in the error sheet to determine the following variables:

[0110] C1: The number of details with serial number in "false unbalanced details (CMPT_FALSE_UNEQUAL)".

[0111] C2: The number of details whose serial numbers are not in the "false unbalanced details (CMPT_FALSE_UNEQUAL)".

[0112] C3: The number of details in the "false uneven details (CMPT_FALSE_UNEQUAL)".

[0113] C4: The number of details whose set number is not in the "false unbalanced details (CMPT_FALSE_UNEQUAL)".

[0114] C0: Detailed quantity of the error sheet.

[0115] False unevenness error handling form information AC_FUE_ERR_FORM

[0116]

[0117]

[0118] S403, processing the target error sheet based on the false uneven error processing information table.

[0119] In some embodiments, the target error handling order can be determined to be successfully matched if and only if the following equation is true: (C1-C2)==C0 or (C3-C4)==C0

[0120] Furthermore, after confirming that the target error order is successfully reconciled, the status of the target error order in the false imbalance error processing order information table can be modified to "reconciled successfully" or "processed", and the target error order can be closed.

[0121] In some embodiments, when the above equation is not satisfied, the target error order cannot be closed automatically, and the error details that do not exist in the target details (which may be information such as the balance set number / serial number of the unbalanced account) can be placed in the remarks field, and the status of the target error order can be set to "pending".

[0122] In some embodiments, the error sheets in the "pending" state in the false uneven error handling sheet information table can be traversed, and based on the error sheet information, including the error type, primary responsible component, transaction service number and other key information in the error sheet basic information, the error sheet is split and processed, and the new error sheet is written into the error sheet main table EH_FORM_INFO. Further, the information and status in the false uneven error handling sheet information table are modified.

[0123] In some embodiments, there are two ways to split the order. One is to split the non-false uneven details from the old error order, that is, to create a new error order based on the non-false uneven details. In this method, the work order processing timeout limit will be recalculated from the creation date of the new error order, which is more reasonable. However, for the accounting component, it is necessary to re-claim the error order, and if an account adjustment plan has been made on the old error order or attachments have been added, these operations will all belong to the old error order, and the new error order needs to be done again. The other is to split the false uneven details from the old error order, that is, to retain the non-false uneven details in the old error order. Specifically, the status of the false uneven details can be set to processed, and the false uneven details can also be distinguished from the non-false uneven details according to the status of the details. This method does not require the accounting component to claim again. If an account adjustment plan has been made or attachments have been added on the old error order, these operations can still be used. However, the time limit for handling the work order will be calculated from the creation date of the original error order, which is unreasonable, and the information of the old error order has changed, so the risk of adjusting the account is high.

[0124] In some embodiments, when processing error tickets, all relevant error ticket information can be queried based on the balance set number or serial number in the false imbalance details and the status of "pending". If the status of all the error tickets involved is "processed", the status of the false imbalance details can be modified to "processed successfully" to prevent repeated processing of the false imbalance details, which would cause a waste of resources.

[0125] Based on the same technical concept, the present application embodiment provides an error sheet processing device, please refer to Figure 5 The device 500 can execute any step in the above error ticket processing method, which will not be described here in order to avoid repetition. The device 500 includes an acquisition module 501 and a processing module 502.

[0126] The acquisition module 501 is used to acquire multiple target details generated on a set date from the accounting engine component, and to acquire error slips generated before the set date from each accounting component; wherein the target details are details that have the same identifier as the details to be settled and have successfully undergone consistency check, the details to be settled are identifiers of details that have failed transaction consistency check before the set date, and the error slips include multiple error details;

[0127] The processing module 502 is used to compare the identifiers of the multiple target details with the identifiers of the error details in the error sheet, and determine at least one target error sheet from the error sheets according to the comparison result; for each target error sheet, process each target error sheet based on obtaining the multiple target details.

[0128] In a possible implementation, the processing module 502, when processing each target error sheet based on obtaining the multiple target details, is specifically configured to:

[0129] Determine the total number of error details in each target error list and the target number of error details corresponding to each target error list, wherein the target number of error details is the number of error details in the target error list having the same identifier as the target detail;

[0130] Matching the total number of error details with the target number of error details;

[0131] The target error ticket is processed based on the matching result.

[0132] In a possible implementation, the processing module 502, when processing the target error ticket based on the matching result, is specifically configured to:

[0133] If the matching result is that the total number of the error details is equal to the target error detail number, the status of each error detail in the target error sheet is changed to a processed status, and the target error sheet is closed;

[0134] If the matching result is that the total number of the error details is greater than the target number of error details, the target error list is modified based on the multiple target details.

[0135] In a possible implementation, the processing module 502, when modifying the target error sheet based on the multiple target details, is specifically configured to:

[0136] According to the identifiers respectively corresponding to the multiple target details, determine N target error details in the target error list having the same identifier as the target detail, where N is a positive integer;

[0137] Creating a new error sheet based on the error details in the target error sheet except the N target error details, and closing the target error sheet;

[0138] The status of each error detail in the new error sheet is set to a pending status.

[0139] In a possible implementation, the processing module 502, when modifying the target error sheet based on the multiple target details, is specifically configured to:

[0140] According to the identifiers respectively corresponding to the multiple target details, determine N target error details in the target error list having the same identifier as the target detail, where N is a positive integer;

[0141] The status of N target error details in the target error list is modified to a processed status, and a new target error detail quantity is determined based on at least one error detail in a pending status in the error list.

[0142] In a possible implementation, when comparing the identifiers of the multiple target details with the identifiers of the error details in the error sheet, the processing module 502 is specifically configured to:

[0143] Determine M error details in the error list whose error detail status is in a pending state, where M is a positive integer;

[0144] For any one of the M error details, the identifier of the any one error detail is compared with the identifiers of the multiple target details.

[0145] In a possible implementation, when determining at least one target error ticket from the error tickets according to the comparison result, the processing module 502 is specifically configured to:

[0146] For each error ticket, when the comparison result is that the identifier of at least one error detail included in the error ticket is the same as the identifier of the target detail, the error ticket is used as the target error ticket.

[0147] Based on the same technical concept, the embodiment of the present application provides an electronic device, which can realize the functions of the error sheet processing device discussed above, please refer to Figure 6 , the device includes a memory 601 and a processor 602.

[0148] Memory 601, used for storing program instructions;

[0149] Processor 602 is used to call the program instructions stored in the memory and execute any step in the error ticket processing method according to the obtained program instructions.

[0150] In the embodiment of the present application, the processor 602 is the control center of the electronic device, which connects various parts of the electronic device using various interfaces and routes, executes various functions of the electronic device and processes data by running or executing software programs / or modules stored in the memory 601, and calling data stored in the memory 601. Optionally, the processor 602 may include one or more processing units. The processor 602, for example, may be a control component such as a processor, a microprocessor, a controller, and may be a general-purpose central processing unit (CPU), a general-purpose processor, a digital signal processing (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, transistor logic devices, hardware components or any combination thereof.

[0151] The memory 601 can be used to store software programs and modules, and the processor 602 executes various functional applications and data processing by running the software programs and modules stored in the memory 601. The memory 601 may mainly include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application required for at least one function, etc.; the data storage area may store data created according to business processing, etc. The memory 601, as a non-volatile computer-readable storage medium, may be used to store non-volatile software programs, non-volatile computer executable programs and modules. The memory 601 may include at least one type of storage medium, for example, it may include flash memory, hard disk, multimedia card, card-type memory, random access memory (Random Access Memory, RAM), static random access memory (Static Random Access Memory, SRAM), programmable read only memory (Programmable Read Only Memory, PROM), read only memory (Read Only Memory, ROM), electrically erasable programmable read only memory (Electrically Erasable Programmable Read-Only Memory, EEPROM), magnetic memory, disk, optical disk, etc. The memory 601 is any other medium that can be used to carry or store the desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited thereto. The memory 601 in the embodiment of the present application can also be a circuit or any other device that can realize a storage function, for storing program instructions and / or data.

[0152] Based on the same inventive concept, an embodiment of the present application provides a computer-readable storage medium, the computer-readable storage medium comprising: a computer program, when the computer program is run on a computer, the computer executes any of the error ticket processing methods discussed above. Since the principle of solving the problem by the above-mentioned computer-readable storage medium is similar to that of the error ticket processing method, the implementation of the above-mentioned computer-readable storage medium can refer to the implementation of the method, and the repeated parts will not be repeated.

[0153] Based on the same inventive concept, the embodiment of the present application also provides a computer program product, which includes: computer program code, when the computer program code is run on a computer, the computer executes any of the error ticket processing methods discussed above. Since the principle of solving the problem by the above computer program product is similar to that of the error ticket processing method, the implementation of the above computer program product can refer to the implementation of the method, and the repeated parts will not be repeated.

[0154] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented in one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that include computer-usable program code.

[0155] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0156] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0157] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of user-operated steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for executing on the computer or other programmable device to implement the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0158] Obviously, those skilled in the art can make various changes and modifications to the present application without departing from the spirit and scope of the present application. Thus, if these modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is also intended to include these modifications and variations.

Claims

1. A method for processing an error ticket, characterized in that: include: Acquire multiple target details generated on a set date from the accounting engine component, and acquire error slips generated before the set date from each accounting component; wherein the target details are details that have the same identifier as the details to be settled and have successfully undergone consistency check, the details to be settled are identifiers of details that have failed transaction consistency check before the set date, and the error slips include multiple error details; Comparing the identifiers of the multiple target details with the identifiers of the error details in the error sheet, and determining at least one target error sheet from the error sheet according to the comparison result; For each target error sheet, each target error sheet is processed based on obtaining the multiple target details.

2. The method according to claim 1, characterized in that The processing of each target error sheet based on obtaining the multiple target details includes: Determine the total number of error details in each target error list and the target number of error details corresponding to each target error list, wherein the target number of error details is the number of error details in the target error list having the same identifier as the target detail; Matching the total number of error details with the target number of error details; The target error ticket is processed based on the matching result.

3. The method according to claim 2, characterized in that The processing of the target error sheet based on the matching result includes: If the matching result is that the total number of the error details is equal to the target error detail number, the status of each error detail in the target error sheet is changed to a processed status, and the target error sheet is closed; If the matching result is that the total number of the error details is greater than the target number of error details, the target error list is modified based on the multiple target details.

4. The method according to claim 3, characterized in that The modifying the target error sheet based on the multiple target details includes: According to the identifiers respectively corresponding to the multiple target details, determine N target error details in the target error list having the same identifier as the target detail, where N is a positive integer; Creating a new error sheet based on the error details in the target error sheet except the N target error details, and closing the target error sheet; The status of each error detail in the new error sheet is set to a pending status.

5. The method according to claim 3, characterized in that The modifying the target error sheet based on the multiple target details includes: According to the identifiers respectively corresponding to the multiple target details, determine N target error details in the target error list having the same identifier as the target detail, where N is a positive integer; The status of N target error details in the target error list is modified to a processed status, and a new target error detail quantity is determined based on at least one error detail in a pending status in the error list.

6. The method according to claim 1, characterized in that The comparing the identifiers of the multiple target details with the identifiers of the error details in the error sheet includes: Determine M error details in the error list whose error detail status is in a pending state, where M is a positive integer; For any one of the M error details, the identifier of the any one error detail is compared with the identifiers of the multiple target details.

7. The method according to any one of claims 1 to 6, characterized in that: The step of determining at least one target error ticket from the error tickets according to the comparison result comprises: For each error ticket, when the comparison result is that the identifier of at least one error detail included in the error ticket is the same as the identifier of the target detail, the error ticket is used as the target error ticket.

8. An error sheet processing device, characterized in that: include: An acquisition module, used to acquire multiple target details generated on a set date from the accounting engine component, and to acquire error slips generated before the set date from each accounting component; wherein the target details are details that have the same identifier as the details to be settled and have successfully undergone consistency check, the details to be settled are identifiers of details that have failed transaction consistency check before the set date, and the error slips include multiple error details; A processing module is used to compare the identifiers of the multiple target details with the identifiers of the error details in the error sheet, and determine at least one target error sheet from the error sheets according to the comparison result; for each target error sheet, process each target error sheet based on obtaining the multiple target details.

9. The device according to claim 8, characterized in that The processing module, when processing each target error sheet based on obtaining the multiple target details, is specifically used to: Determine the total number of error details in each target error list and the target number of error details corresponding to each target error list, wherein the target number of error details is the number of error details in the target error list having the same identifier as the target detail; Matching the total number of error details with the target number of error details; The target error ticket is processed based on the matching result.

10. The device according to claim 9, characterized in that The processing module, when processing the target error sheet based on the matching result, is specifically used to: If the matching result is that the total number of the error details is equal to the target error detail number, the status of each error detail in the target error sheet is changed to a processed status, and the target error sheet is closed; If the matching result is that the total number of the error details is greater than the target number of error details, the target error list is modified based on the multiple target details.

11. The device according to claim 10, characterized in that The processing module, when modifying the target error sheet based on the multiple target details, is specifically used to: According to the identifiers respectively corresponding to the multiple target details, determine N target error details in the target error list having the same identifier as the target detail, where N is a positive integer; Creating a new error sheet based on the error details in the target error sheet except the N target error details, and closing the target error sheet; The status of each error detail in the new error sheet is set to a pending status.

12. The device according to claim 10, characterized in that The processing module, when modifying the target error sheet based on the multiple target details, is specifically used to: According to the identifiers respectively corresponding to the multiple target details, determine N target error details in the target error list having the same identifier as the target detail, where N is a positive integer; The status of N target error details in the target error list is modified to a processed status, and a new target error detail quantity is determined based on at least one error detail in a pending status in the error list.

13. The device according to claim 8, characterized in that The processing module, when comparing the identifiers of the plurality of target details with the identifiers of the error details in the error sheet, is specifically used to: Determine M error details in the error list whose error detail status is in a pending state, where M is a positive integer; For any one of the M error details, the identifier of the any one error detail is compared with the identifiers of the multiple target details.

14. The device according to any one of claims 8 to 13, characterized in that: The processing module, when determining at least one target error ticket from the error tickets according to the comparison result, is specifically used to: For each error ticket, when the comparison result is that the identifier of at least one error detail included in the error ticket is the same as the identifier of the target detail, the error ticket is used as the target error ticket.

15. An electronic device, characterized in that: include: A memory for storing program instructions; A processor is used to call the program instructions stored in the memory, and execute the method according to any one of claims 1 to 7 according to the obtained program instructions.

16. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, wherein the computer program includes program instructions, and when the program instructions are executed by a computer, the computer executes the method according to any one of claims 1 to 7.

17. A computer program product, characterized in that The computer program product comprises: a computer program code, and when the computer program code is run on a computer, the computer is enabled to execute the method according to any one of claims 1 to 7.

Images