IDoc to CSV on multiple folders based on field in IDoc

HI Experts,

My scenario is IDoc to CSV and vice versa CSV to IDoc. Let us say IDoc to CSV as Outbound and CSV to IDoc is Inbound here. Please find the below requirements interface wise.

Outbound scenario: IDoc --> CSV

All the end users who has access to SAP system would be entering the ORDERS01 IDocs manually from different mines, a background job will be executed to fetch all the IDocs in a day and would be triggered to SAP PI 7.31 single stack. Based on the value of WERKS field in IDoc received all the IDocs relating to one mine [or same WERKS value] should be transformed as CSV file with each IDoc data as a single line item and should be posted to the corresponding folders that are created based on the name of the mine on receiver file system. I have done IDoc packaging on the SAP system side and settings on the channel to receive multiple IDocs at a time, FCC receiver and corresponding changes accordingly and the scenario is working like multiple IDocs to single folder only for example if 50 ORDERS01 IDocs are triggered from SAP then a CSV file with 50 line items is getting created and posting to a single folder.Now the requirement is in addition or modification to the above, suppose 70 ORDERS01 IDocs with different values are triggered from with different value to WERKS field and in PI those multiple IDocs with same WERKS value should be categorized as a group and should be transformed to one CSV file with each IDoc as single line item. Can you please suggest some standard ways like variable substitution to achieve this.

Inound scenario: CSV --> IDoc

The requirement is like the end users of file system will place the CSV files on specific Inbound different folders and PI system will poll them and all of them should be triggered as DELVRY07 to SAP R3 from SAP PO and currently the settings in such the interface is working like from single folder a file should be picked and based on the number of line items that many number of IDocs should be triggered to SAP R3.

Kindly suggest standard ways to achieve them.

Thanks,

Nithin.