approved in BP Requisition Management module, also you should be aware that this table resides in DYNAMICS database and so it has CompanyID field. You should compare company ID with GP SY01500 table, which also resides in Dynamics database, but it is MiIn this small article we will try to orient you on how to create cross-product reports, based on SQL view or stored procedure, where data is pulled from Microsoft Great Plains as well as Microsoft Business Portal tables. This query architecture should open for you report designer or programmer the way to create cross-product report. Good example would be the following – life cycle of purchase request, which originates in Business Portal Requisition Management module and then, when approved is moved to Purchase Order in Microsoft Dynamics GP purchase order processing module. The reporting tool selection in our opinion is the secondary question – both popular tools: Crystal Reports and Microsoft SQL Server Reporting Services (SRS) will do the job as soon as you could trust your view or stored procedure. Let’s try to create cross-product query in Requisition Management linking to GP Purchase Order Processing

• ReqMgmtDocument table. This table stores all your purchase requests created, submitted and approved in BP Requisition Management module, also you should be aware that this table resides in DYNAMICS database and so it has CompanyID field. You should compare company ID with GP SY01500 table, which also resides in Dynamics database, but it is Mic

en for you report designer or programmer the way to create cross-product report. Good example would be the following – life cycle of purchase request, which originates in Business Portal Requisition Management module and then, when approved is moved to Purchase Order in Microsoft Dynamics GP purchase order processing module. The reporting tool selection in our opinion is the secondary question – both popular tools: Crystal Reports and Microsoft SQL Server Reporting Services (SRS) will do the job as soon as you could trust your view or stored procedure. Let’s try to create cross-product query in Requisition Management linking to GP Purchase Order Processing

• ReqMgmtDocument table. This table stores all your purchase requests created, submitted and approved in BP Requisition Management module, also you should be aware that this table resides in DYNAMICS database and so it has CompanyID field. You should compare company ID with GP SY01500 table, which also resides in Dynamics database, but it is Mi

rchase Order in Microsoft Dynamics GP purchase order processing module. The reporting tool selection in our opinion is the secondary question – both popular tools: Crystal Reports and Microsoft SQL Server Reporting Services (SRS) will do the job as soon as you could trust your view or stored procedure. Let’s try to create cross-product query in Requisition Management linking to GP Purchase Order Processing

• ReqMgmtDocument table. This table stores all your purchase requests created, submitted and approved in BP Requisition Management module, also you should be aware that this table resides in DYNAMICS database and so it has CompanyID field. You should compare company ID with GP SY01500 table, which also resides in Dynamics database, but it is Mi

as you could trust your view or stored procedure. Let’s try to create cross-product query in Requisition Management linking to GP Purchase Order Processing

• ReqMgmtDocument table. This table stores all your purchase requests created, submitted and approved in BP Requisition Management module, also you should be aware that this table resides in DYNAMICS database and so it has CompanyID field. You should compare company ID with GP SY01500 table, which also resides in Dynamics database, but it is Mi

approved in BP Requisition Management module, also you should be aware that this table resides in DYNAMICS database and so it has CompanyID field. You should compare company ID with GP SY01500 table, which also resides in Dynamics database, but it is Microsoft Dexterity table and it is within GP architecture realm.

• POP tables. In Microsoft Dynamics GP you should know the posting workflow. For the most of transaction types GP is batch processing system, however Purchase Order is an exception – it has statuses and PO lifecycle is the change of statuses. However when you receive against purchase orde – purchase receipt transaction is batch oriented and you can post either individual transaction (in this case the batch number will be your user id) or the whole butch upon the approval. Tools->Resource Description->Tables in GOP workstation will give you the names of the tables in POP, if you switch series to Purchasing. More likely you will need to research the following tables: POP10100 – Purchase Order Work, POP30100 – Purchase Order History (it goes to history when all the lines are received), POP10300 – Purchase Receipt Work, POP30300 – Purchase Receipt History

• SQL View or Stored Procs creation. As you can mention, both products – Micr