Add Two Additional fields to Fulfillment Fact Entity #13
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
What data is expected in fulfilled by field? Where will we get it? |
It's the User login ID that fulfilled the Item, It will be available in the OrderStatus Entity which is already being used |
|
That is usually a facility login. Not the actual person that fulfilled the order. So how is that beneficial? We already have the facility on the order item |
|
I have not asked about its requirements. It is included in the sales report, so I just added it. |
|
@dt2patel sir, FulfilledBy field helps to track the manual completions. |
|
Makes sense. |
dt2patel
approved these changes
Dec 24, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Part of the Issue #12
Requirements
These two newly defined fields are required in the SM-specific report Sales by Item Level