Skip to content
This repository has been archived by the owner on Apr 22, 2024. It is now read-only.

Full Flow issues #116

Open
23 of 28 tasks
Vigneshsekar opened this issue Feb 19, 2020 · 6 comments
Open
23 of 28 tasks

Full Flow issues #116

Vigneshsekar opened this issue Feb 19, 2020 · 6 comments

Comments

@Vigneshsekar
Copy link
Contributor

Vigneshsekar commented Feb 19, 2020

@saiindhu
Copy link
Contributor

saiindhu commented Feb 24, 2020

PR #122 though merged is commented in the code as we modified the parent function.

We did not have the info that are being passed to your function. Can you check that in the dc_return_items_vignesh branch and modify?

@karthikeyan5

@karthikeyan5
Copy link
Contributor

karthikeyan5 commented Feb 26, 2020

the required changes have been made and pushed to the same branch dc_return_items_vignesh... in commit c6d38c6

@Vigneshsekar
Copy link
Contributor Author

Vigneshsekar commented Mar 18, 2020

  • Lot print format (@bharathbiju )

  • Knitting DC not working, Need to add HTML table from LOT in Knitting DC (@bharathbiju )

  • Index out of range issues when supplier doesn't have address. Fix that and add error messages.
    (@bharathbiju )

  • Add totals, secondary qts in DC (@bharathbiju )

  • GRN print formatc (@bharathbiju )

  • Additional parts to be names appropriately, create their templates, map their sizes and test the IPD submission (@saiindhu )

  • Colour mapping of additional parts not added in label fusing (@KaviyaPeriyasamy )

  • Verify BOM duplicates (@KaviyaPeriyasamy )

  • Piece printing issue (@KaviyaPeriyasamy )

  • Extra Yarn in Lot when multiple IPDs are submitted (@KaviyaPeriyasamy )

  • Add location addition in Lot (@M0hammedHaris )

  • Store warehouses are location wise (@M0hammedHaris )

  • Add delivery location in DC delivery items table and make stock transfers accordingly. Allow transfer later option. Related change to print format. Collaborate with BB. (@M0hammedHaris )

@Vigneshsekar
Copy link
Contributor Author

Vigneshsekar commented Mar 18, 2020

  • Naming series of Lot
  • Verify required materials with Kumari/Saravanan for Lot
  • Receive item in excess in GRN than expected
  • Consider corrections in unnecessary additional flows
  • Link process doctype in supplier
  • Adjustments in DC based on delivery quantity than the available quantity.
  • Reorder Expect return items at column
  • Rounding off yarn to bags while making PO/Lot
  • Price list for all the processes
  • Change yarn secondary quantity as bags
  • Filters of Get items expected in return button
  • Change print format headings
  • Permissions management
  • Do we always have to repack as we have to match the name of the item in the order management system?

@Vigneshsekar
Copy link
Contributor Author

Vigneshsekar commented May 11, 2020

Priority Issues

  • Default Material Request Type for accessories
  • Expected Items in return to fetch delivery quantity in DC
  • Polo BOM bug for stitched cloth
  • Alpha gym style BOM bug - related to assorted parking
  • Delivery quantity in DC to be filled from the expected quantity.
  • Rewrite PF
  • Stock adjustment by automating Journal entries (Decided to do it manually)
  • PF item code has too much info (in dyeing GRN)
  • in GRN Error on receiving extra qty
  • Add delivery location in DC delivery items table and make stock transfers accordingly.
  • Delivery location in DC Related change to print format.
  • Rounding off yarn to bags while making PO/Lot
  • Permissions management
  • From address mentioning in DC
  • remove item linking from process doctypes. take it from the IPD instead.

UX/Minor Issues

  • "Material Request Plan Item" Table in Lot to be sorted
  • Precision in DC prints
  • Show tables from LOT in knitting DC
  • status of POs doesn't change from "to receive" ever after GRN is submitted
  • Naming series of Lot
  • Consider corrections in unnecessary additional flows
  • Link process doctype in supplier
  • Change yarn secondary quantity as bags
  • hide is_combined after part is created

Doubts

  • Check DC 5583
  • Is rolls needed in the knitting print format
  • Discuss the whole dyeing DC/GRN workflow
  • Handle BOM in PO from DC for the additional process
  • Verify BOM duplicates
  • Do we always have to repack as we have to match the name of the item in the order management system?
  • how to handle 2 types of IPD for single item... (i.e. versioning of IPD and the BOM tree)
  • general DC for machines repairs and all... how to handle?
  • Lot creation in Polo
  • how to test new IPDs in production? Come up with IPD import, export tool?
  • new ratio and avg weight for each lot in boss back Patti... how to handle? expedite versioning feature?

Data fixes

  • change Green Lable to GL in item attri abbreviation
  • add folding in polo gym stitching

Helpers

  • have to add entry helper fields and buttons in DC
  • Add helper for Expected items in return. An idea related to cutting DC to give them order to cut for the item of a particular size.
  • Make sure cutting GRN entry is easy with available helpers

@Vigneshsekar
Copy link
Contributor Author

Vigneshsekar commented May 23, 2020

  • Order by Dia in return materials table in DC

<Helper Section>

  • In GRN, if the total is given, split them across the items.
  • In DC, Copy over is required
  • In DC for Cutting, for size and colour, if the number of pieces is given, Return Materials table needs to be populated

</Helper Section>

  • IN GRN, if partially received, only the remaining qty to be shown in the next GRN of the same lot/process.
  • Key error supply qty: Not all the delivery items has to be GRNed, when making DC. Partly is fine.
  • Receive in excess has to be set for all items.
  • Knitting Dia will be carried from first to the last step. Compacting Dia is just a point of information. But will not be used in change of name or item attribute. This is because Compacting Dia will keep changing. A roll can be sent back to compacting to modify dia multiple times.
  • What to do about cancelling the DC and GRN?

.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants