0
Category:
STATUS DETAILS

Comments

I have just been instructed to stop using phantoms in BOM because the "Routing become full of junk"The Routing posts the phantom items to the top of the list. We just want it to be parts of the parents assembly routing, as a phantom.This suggestion would solve this problem.

Category:

I just saw this in Yammer and realized this is finally happening!! Super excited!

Category:

This feature is required. Even a normal vendor return process is required through AWS.

Category:

Acknowledging the above.Category page showing up with OUN & Record Id is really cumbersome for the user to understand.

Category:

Am I wrong or is it not in the "Wave 1 2024" release?

Category:

Our customers are asking for this functionality as well.

Category:

Are we then expecting a sales invoice per shipment (packing slip) grouped by vat registration number? if you allow different registration numbers on sales order lines with 1 or multiple packing slips that would make sense. You cant have different vat registration numbers on the same invoice legally. i think. Otherwise i will assume you can maybe create queries to batch invoice based on this information for the packing slips to solve the problem..

Category:

Ind AS 9 is the Indian version of IFRS 9 just for reference purposes.The provisions mentioned across both are similar in nature. Also this functionality should not only be made limited to Lease accounting however quite a few scenarios the same is applicable, for example - Security deposit paid to Open a Franchisee, Security deposit paid to Govt. authorities for licenses, Security deposit paid to Electricity power distribution company etc. Thus a separate module if can be made would be really appreciated with an option to link the same with leases.

Category:

This would be so useful in several use cases, not least the one in the original post. I hope it is implemented. Just needs a check for partially/fully shipped or invoiced, and some rewritten code to cope with assembly orders.

Category:

I'm trying to understand your requestYou do have the option to check if an Fieldref exist and then assign the Fieldref, so why do you need more?var  MyRecordRef: RecordRef;  i: Integer;  VarFieldName: FieldRef;  Text000: Label 'The %1 table contains %2 field\(s\).\\';begin    MyRecordRef.Open(18);    for i := 1 to 12 do begin     if MyRecordRef.FieldExist(i) then begin       VarFieldName := MyRecordRef.Field(i);       Message(Text000, i, VarFieldName.Name);      end else      Message(Text001, i);     end;  end;

Category:

  • 1
  • 483
  • 484
  • 485
  • 486
  • 487
  • 488
  • 489
  • 490
  • 491
  • 500