• Credit Management workflow does not stick to the focus on the specific record for approval.

    Problem:

    When selecting a workflow work item that is assigned to a user it will open the entire list of credit holds, not the specific credit hold assigned. 


    Re-pro:

    Credit Management workflow does not stick to the focus on the specific record for approval.

    Pre-requisites – Credit management workflow

    Navigate to credit and collections > setup > Credit management workflows.


    Workflow elements with approval.

    Credit and collections > Setup > Credit management setup > Blocking rules

     

    Scenario

    Created sale order for the customer defined in the blocking rules.


    The moment sales order created and saved; it will reflect for the credit management approval in ‘Default Dashboard’.

    Once an approval user click on the record to approve system open up the form below with the details.

    Here the user doesn’t see any details for approval (e.g., sales order total), hence they navigate to specific Id to view the details for next action.


    If we could see here the moment form is an opened system filtering all the records instead of the desired record to be approved. Due to which each record user has to filter the credit hold ID for the next action.

    Which is time consuming activity daily.

     

    Actual result: System doesn’t filter the desired record to be approved.


    Expected result: System should filter the desired record to be approved.


  • Reporting for multiple VAT registrations for Lithuanian Country-region [Intrastat]

    According to the standard MS document, It is not allowed for Lithuanian country region to generate the Intrastat report, when Lithuanian country has been selected as added country/region as part of Multiple VAT registrations functionality.


    Customer statement-

    Lithuanian is not a small country; it operates on huge number of transactions. Along with that customer has configured the Multiple VAT registration setup in their environment and now they are struggling to generate this reporting's.


    Requesting the Product group team to help customer, by considering this country/region as per of Multiple VAT registration configuration.

  • Post project invoice proposal form brings Open and Approved transactions for posting, despite project invoice proposals workflow is enabled

    Customer is using form called “Post project invoice proposals” (Project management and accounting > Periodic > Project Invoices > Post project invoice proposals) to post the ‘Approved’ Invoice proposal created.

    Here customer is getting invoice proposals with the status of ‘Approved’ as well as status Open’ and Open status are being considered for posting. Instead of only Approved Invoice proposals and sent to the clients.


    The system is just not only showing Open project invoice proposals in the form, but it posts them without passing through the workflow approval process.

     

    Customer is having misplaced information on posting of Invoice proposal. It's allowed to post project invoice proposals without being approved.


    The expected behavior is that only the invoice proposals that are set as ‘Approved’ should only be considered for posting, when there's workflow is enabled strictly.

    


  • [ITA] Number sequence group wise Project invoice and voucher number for PMA

    Project-wise number sequence functionality for invoices and vouchers is not available. However, this functionality is present for free text invoices and sales order invoices. It is surprising because after mapping different number sequence groups on the customer master level and seeing it work for FTI and SO invoices, it should work for all customer invoices regardless of where they are generated from within the system.


    Only number sequence group creation option is available in Project accounting and management parameter. However, that number sequence group is not populating on the creation project and as a result system is picking only one voucher sequence from the parameter and not from attached group to the customer which been selected as funding resource.


    Expectation: Functionality should work for all customer invoices regardless of where they are generated from within the system.