-
Notifications
You must be signed in to change notification settings - Fork 61
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[EDCC] Add new object type for EDCC #661
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi, thank you for your aff. Definitely one of the biggest I have seen :)
{ | ||
"formatVersion": "1", | ||
"header": { | ||
"description": "AFF type for EDCK", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"description": "AFF type for EDCK", | |
"description": "AFF type for EDCC", |
What does EDCC stand for?
message_type_description TYPE ty_short_description, | ||
"! <p class="shorttext">Tax Authority Document Type</p> | ||
"! Tax authority document type | ||
taxauth_documenttype TYPE c LENGTH 20, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
tax_authority_document_type
original_language TYPE zif_aff_types_v1=>ty_original_language, | ||
END OF ty_message, | ||
"! <p class="shorttext">Tax Authority Message Types</p> | ||
"! Tax Authority Message types |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"! Tax Authority Message types | |
"! Tax authority message types |
Sentence case
@GuilhermeSaraiva96 : I have incorporated the above suggested changes. Please have a look and suggest if we can have a meeting to understand this AFF. |
@GuilhermeSaraiva96 : Let us know if the AFF requires further adjustment |
Hi, thank you for your changes, looks good already. I have just a few more suggestions. Additionally, could you please send a meeting request so that we can discuss the whole AFF before moving to the UX review? Thanks! |
@GuilhermeSaraiva96 : I have regenerated the examples and incorporated changes related to description of objects coming from other object types like EDCR/EDCK. Additionally I have added one new node in the AFF in ty_main, additional_selection_fields. Please have a look and let me know. |
From my side, it is ready for the UX-Review. @nicolas? |
@GuilhermeSaraiva96 : Above comments are fixed. please have a look |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! Looks good. Next time you can mark the comments as resolved, so that it is also easier to follow what has been changed, and what hasn't. Good job!
ready for UX Review |
"! <p class="shorttext">Country</p> | ||
"! Country | ||
"! $required | ||
country TYPE c LENGTH 3, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you please put the country field into a structure general_information
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please see my comments
"! <p class="shorttext">Country</p> | ||
"! Country | ||
"! $required | ||
country TYPE c LENGTH 3, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What is this language field about? Are there any texts that must be translated?
"! <p class="shorttext">Table Name</p> | ||
"! Table name | ||
table_name TYPE zif_aff_types_v1=>ty_object_name_30, | ||
"! <p class="shorttext">Field Name</p> | ||
"! Field name | ||
field_name TYPE zif_aff_types_v1=>ty_object_name_30, | ||
"! <p class="shorttext">Field Type</p> | ||
"! Field type | ||
field_type TYPE ty_field_type, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there any mandatory field? With this setting, I could add an entry to the table that is completely empty having only fieldType: selectOption
"! <p class="shorttext">Table Name</p> | ||
"! Table name | ||
table_name TYPE zif_aff_types_v1=>ty_object_name_30, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Shouldn't this be required? Or can table_name be empty?
"! <p class="shorttext">Comparison Type</p> | ||
"! Comparison type | ||
"! $required | ||
comparison_type TYPE zif_aff_types_v1=>ty_object_name_30, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should be enough:
"! <p class="shorttext">Comparison Type</p> | |
"! Comparison type | |
"! $required | |
comparison_type TYPE zif_aff_types_v1=>ty_object_name_30, | |
"! <p class="shorttext">Name</p> | |
"! Comparison type | |
"! $required | |
name TYPE zif_aff_types_v1=>ty_object_name_30, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Besides that, is this an ABAP object? Or is this something that is defined in the EDCC object.
I wondered whether the description of the comparison type is correctly stored here
"! <p class="shorttext">Comparison Type Description</p> | ||
"! Description of the comparison type | ||
"! $required | ||
description TYPE ty_long_description, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same here:
"! <p class="shorttext">Comparison Type Description</p> | |
"! Description of the comparison type | |
"! $required | |
description TYPE ty_long_description, | |
"! <p class="shorttext">Description</p> | |
"! Description of the comparison type | |
"! $required | |
description TYPE ty_long_description, |
"! <p class="shorttext">eDocument Type Assignment</p> | ||
"! Assign eDocument types associated with consistency scenario | ||
edocument_types TYPE ty_edoc_types, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"! <p class="shorttext">eDocument Type Assignment</p> | |
"! Assign eDocument types associated with consistency scenario | |
edocument_types TYPE ty_edoc_types, | |
"! <p class="shorttext">eDocument Types</p> | |
"! Assign eDocument types associated with consistency scenario | |
edocument_types TYPE ty_edoc_types, |
"! eDocument Type | ||
edoc_type TYPE c LENGTH 10, | ||
END OF ty_edoc_type. | ||
"! <p class="shorttext">eDocument Type Assignment</p> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"! <p class="shorttext">eDocument Type Assignment</p> | |
"! <p class="shorttext">eDocument Types</p> |
"! <p class="shorttext">eDocument Type</p> | ||
"! eDocument Type | ||
edoc_type TYPE c LENGTH 10, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Or only
"! <p class="shorttext">eDocument Type</p> | |
"! eDocument Type | |
edoc_type TYPE c LENGTH 10, | |
"! <p class="shorttext">Type</p> | |
"! eDocument Type | |
type TYPE c LENGTH 10, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should this be a mandatory field?
"! <p class="shorttext">Inconsistency Category</p> | ||
"! Inconsistency category | ||
result_ui_group TYPE ty_resultgroup, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"! <p class="shorttext">Inconsistency Category</p> | |
"! Inconsistency category | |
result_ui_group TYPE ty_resultgroup, | |
"! <p class="shorttext">Category</p> | |
"! Inconsistency category | |
category TYPE ty_resultgroup, |
country_xtension TYPE zif_aff_types_v1=>ty_object_name_30, | ||
"! <p class="shorttext">Result Processes</p> | ||
"! Assign result process to the UI group | ||
result_process TYPE ty_result_processes, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These result processes have been there before (field of checks). Do we need them twice?
No description provided.