SAP Note
3065034 - eDocument framework: Missing Buttons in EDOC_COCKPIT, Match
Documents Action, in Languages Other than English
Component: CA-GTF-CSC-EDO-BR (Cross-Application Components > General Application Functions >
Country/Region -Specific Application Interface Objects > Electronic Document Processing Framework >
Inbound Nota Fiscal), Version: 1, Released On: 02.07.2021
Symptom
You log on to the eDocument Cockpit (EDOC_COCKPIT) transaction in a language other than English. Then, in
the Match Documents action, you don't see some of the buttons (for example, Save, Log).
Other Terms
eDocument, eDoc, eInvoicing, e-Invoicing, electronic invoice, electronic invoicing, e-document, e-Document, e-Docs, e-Doc,
e-docs, e-doc, Match Documents, EDOMATCHBTNT, cluster view EDOC_MATCH.
Reason and Prerequisites
This SAP Note contains a report and automatic correction instructions to create/modify objects that are used in the solution
delivered by this SAP Note.
Solution
This SAP Note delivers the correct table definition for the text table EDOMATCHBTNT, which enables the translation.
After apply this SAP Note, see SAP Note 3063070 for delivery information and proper instructions on how to translate the
table EDOMATCHBTNT.
The tables and structures that need translation for Match Documents are the following:
eDocument Match: Buttons Texts (EDOMATCHBTNT)
eDocument Match: Types Description (EDOMATCHTYPET)
eDocument Match: Search Grid Fields (EDOC_MATCH_FLD_SEARCH)
eDocument Match: Match Grid Fields (EDOC_MATCH_FLD_MATCH)
Use transaction SNOTE to implement the attached correction instructions.
Version Date Reason
01 July 02, 2021 Released for Customer
As a general rule SAP recommends that you implement the Support Package specified for your release. However, if you need
to install a solution earlier, use the SAP Note Assistant to implement the correction instruction. You can find more
information about the SAP Note Assistant in SAP Support Portal, under SAP Note Assistant.
Manual Activities
------------------------------------------------------------------------
|Manual Pre-Implement. |
------------------------------------------------------------------------
|VALID FOR |
|Software Component SAP_APPL SAP Application |
| Release 600 SAPKH60001 - SAPKH60033 |
| Release 602 Until SAPKH60223 |
| Release 603 Until SAPKH60322 |
| Release 604 SAPKH60401 - SAPKH60423 |
| Release 605 Until SAPKH60520 |
| Release 606 SAPKH60601 - SAPKH60627 |
| Release 617 SAPKH61701 - SAPKH61722 |
| Release 618 Until SAPK-61816INSAPAPPL |
------------------------------------------------------------------------
Caution: You have to perform this manual pre-implementation step manually and separately in each system before
you import the Note to implement.
MANUAL STEP
In order to implement the changes delivered by this correction note follow the steps next:
01. Since report NOTE_3065034 has been developed to be executed in English only, we recommend that you log on in
English.
02. In transaction SA38, select report NOTE_3065034 and select #Execute#.
03. Select "TESTRUN" and execute the report.
04. Check the Simulation Log and ensure that all the messages have a green traffic light. If there are any
warnings and/or error messages that you cannot solve yourself, create a customer incident under the
corresponding component of NOTE_3065034.
05. Go back (choose "Back" or F3), select "UPDATE & ACTIVATE", and execute the report again.
06. The system prompts you to either activate your objects online or in batch mode. The online mode is
recommended as this enables you to see any activation issues immediately. Use the batch mode option only if
activation in online mode fails with a time out.
07. Within the Change Log, the system displays a list of all objects processed. Ensure that all the displayed
messages are warnings or information messages. If there are any warnings and/or error messages that you cannot
solve yourself, create a customer incident under the corresponding component of NOTE_3065034. If you have
selected to activate the objects in batch mode (see step 6), check the activation log of the job as explained in
the message text of the Detailed Log.
08. If you have to generate maintenance views, you will see the GENVIEW step on the selection screen of report
NOTE_3065034. Execute this step.
09. Optional: Go back (choose "Back" or F3), select "SHOWLOGS", and execute the report again.
10.Select the node with the last execution log (according to the date and time) and ensure that there are only
information messages (green traffic lights). If there are any warnings and/or error messages that you cannot
solve yourself, create a customer incident under the corresponding component of NOTE_3065034.
11. If any inactive objects are detected during the release of your transports, execute the "UPDATE & ACTIVATE"
step again.
Software Components
Software Component From To
SAP_APPL 600 600
SAP_APPL 602 602
SAP_APPL 603 603
SAP_APPL 604 604
SAP_APPL 605 605
SAP_APPL 606 606
SAP_APPL 617 617
SAP_APPL 618 618
S4CORE 101 101
S4CORE 102 102
S4CORE 103 103
S4CORE 104 104
S4CORE 105 105
Correction Instructions
Software Component Number of Correction Instructions
SAP_APPL 12
S4CORE 5
Prerequisites
Software Component From To SAP Note/KBA Title Component
S4CORE 101 101 2805721 Prerequisite objects for SAP Note 2774109 CA-GTF-CSC-EDO-BR
S4CORE 102 102 2805721 Prerequisite objects for SAP Note 2774109 CA-GTF-CSC-EDO-BR
S4CORE 103 103 2805721 Prerequisite objects for SAP Note 2774109 CA-GTF-CSC-EDO-BR
SAP_APPL 605 605 2805721 Prerequisite objects for SAP Note 2774109 CA-GTF-CSC-EDO-BR
SAP_APPL 606 606 2805721 Prerequisite objects for SAP Note 2774109 CA-GTF-CSC-EDO-BR
SAP_APPL 617 617 2805721 Prerequisite objects for SAP Note 2774109 CA-GTF-CSC-EDO-BR
SAP_APPL 618 618 2805721 Prerequisite objects for SAP Note 2774109 CA-GTF-CSC-EDO-BR
Support Package
Software Component Version Support Package
S4CORE 101 SAPK-10111INS4CORE
S4CORE 102 SAPK-10209INS4CORE
S4CORE 103 SAPK-10307INS4CORE
S4CORE 104 SAPK-10405INS4CORE
S4CORE 105 SAPK-10503INS4CORE
SAP_APPL 600 SAPKH60034
SAP_APPL 602 SAPKH60224
SAP_APPL 603 SAPKH60323
SAP_APPL 604 SAPKH60424
SAP_APPL 605 SAPKH60521
SAP_APPL 606 SAPKH60628
SAP_APPL 617 SAPKH61723
SAP_APPL 618 SAPK-61817INSAPAPPL
