In this article
Resource Card
Use this page to create, modify, and delete resources. For more information, see the Microsoft Dynamics 365 Business Central documentation.
Resource Entity Examples
The owner entity for the Resource LINA is SALES. On the Sales Invoice page, the following transaction is created:
-
The header entity is ADM.
-
The line entity is ADM.
| General | ||||||
| Entity Code | ADM | Contact | Robert Townes | Due Date | May 8, 2019 | |
| Customer Name | Adatum Corporation | Posting Date | April 8, 2019 | Allocation Template | ||
| Lines | ||||||
| Entity Code | Type | No. | Description | Allocation Template | Location Code | Quantity |
| ADM | Resource | LINA | ||||
The preview of the General Ledger entries is as follows:
| Department Code | Posting Date | G/L Account No. | Description | Amount | Bal. Account Type |
| SALES | April 8, 2019 | 40100 | Invoice S-INV102227 | -139.00 | G/L Account |
| SALES | April 8, 2019 | 10600 | Due From ADM | 139.00 | G/L Account |
| ADM | April 8, 2019 | 10300 | Due To SALES | -139.00 | G/L Account |
| ADM | April 8, 2019 | 10400 | Invoice S-INV102227 | 139.00 | G/L Account |
-
The entity for the resource account 40100 is SALES (based on the owner entity of the resource).
-
Because the entity of the resource account (SALES) is different from the header entity (ADM), Intercompany distributions are processed.
The Resource Ledger Entry will also be assigned with SALES (based on the owner entity of the resource).
| Department Code | Posting Date | Resource No. | Description | Quantity | Amount |
| SALES | April 8, 2019 | LINA | Invoice S-INV102227 | 1 | -139.00 |
The same example can be used for Purchases and Service Transactions. On the Project page, the following transaction is created:
-
The header entity is ADM.
-
The line entity is ADM.
| General | ||||||
| Entity Code | ADM | Start Date | March 1, 2023 | End Date | March 31, 2023 | |
| Customer Name | Adatum Corporation | WIP Method | POC | WIP Posting Method | Per Project Ledger Entry | |
| Project No. | JOB001 | |||||
| Lines | ||||||
| Entity Code | Project Task | Project Task Type | ||||
| ADM | 100 | Posting | ||||
| Project Planning Lines | ||||||
| Project Task No. | Type | No. | Quantity | |||
| 100 | Resource | LINA | 1 | |||
Go to Project journal and post the Resource LINA.
Go to Projects page and choose JOB0001, run “Calculate WIP” and you should see the below WIP entries created: -
| Department Code | WIP Posting Date | Project No. | G/L Account No. | Type | WIP Amount |
| SALES | 04/12/23 | JOB001 | ResourceCostApply | Applied Cost | -75.90 |
| ADM | 04/12/23 | JOB001 | 40250 | Recognized Costs | -139.00 |
| ADM | 04/12/23 | JOB001 | 50300 | Recognized Costs | 75.90 |
The entity for the resource account “ResourceCostApply” is SALES (based on the owner entity of the resource).
Run “Post WIP To G/L” and you should see below entries:
| Department Code | WIP Posting Date | Project No. | G/L Account No. | Type | WIP Amount |
| SALES | 04/12/23 | JOB001 | ResourceCostApply | Applied Cost | -75.90 |
| ADM | 04/12/23 | JOB001 | 40250 | Recognized Costs | -139.00 |
| ADM | 04/12/23 | JOB001 | 50300 | Recognized Costs | 75.90 |
Click on Entry > Find Entries > G/L Entry and you should see below entries.
| Department Code | Posting Date | G/L Account No. | Description | Amount | Bal. Account Type | Balance Account No. |
| SALES | 04/12/23 | ResourceCostApply | WIP Projects | -75.90 | G/L Account | |
| SALES | 04/12/23 | 10600 | Due from ADM | 75.90 | G/L Account | |
| ADM | 04/12/23 | 10300 | Due to SALES | -75.90 | G/L Account | |
| ADM | 04/12/23 | 10950 | WIP Projects | 75.90 | G/L Account | |
| ADM | 04/12/23 | 50300 | Recognition Project | 75.90 | G/L Account | 10950 |
| ADM | 04/12/23 | 10950 | Recognition Project | -75.90 | G/L Account | 50300 |
| ADM | 04/12/23 | 40250 | Recognition Project | -139.00 | G/L Account | 10910 |
| ADM | 04/12/23 | 10910 | Recognition Project | 139.00 | G/L Account | 40250 |
Since the entity of the resource account “ResourceCostApply” (SALES) is different from the header entity (ADM), intercompany distributions are added for the resource.
Use Time Sheets
If you use time sheets, ensure that you turn on the Use Time Sheet option, which is useful when using the suggest time sheet feature for time sheets that have been submitted and approved. For more information, see the Microsoft Dynamics 365 Business Central documentation.
Fields
This screen contains the following MEM fields, but these are optional if Resource Owner Mandatory is not marked on MEM Multi Entity Management Setup page.
| Field | Description |
| Shortcut Dimension 1 Code |
Select the owner entity for the record if Dimension 1 is used as MEM Entity. |
| Shortcut Dimension 2 Code |
Select the owner entity for the record if Dimension 2 is used as MEM Entity. |
Note: The user cannot change the owner entity once any transaction is posted for the resource. In this case, create a new Resource in case the Resource is now used by another entity.
Assign Entity Security to a Resource
To assign entity security to a resource record, follow the steps in the Microsoft Dynamics 365 Business Central documentation for creating or editing a customer record, and incorporate the following steps:
- Select Actions > MEM Assign Entity Security.
- On the MEM Master Security page, check that the Direction, Master Records, and corresponding record field are updated with the values you want.
- In the Destination Lines, select one or more entities for the relationship.
- Close the MEM Master Security page to return to the card page for the record.
These fields are automatically updated based on the selected record and cannot be changed.
For new records, your default entity or the first entity (if no default entity is selected) in the list is automatically assigned to the record.
Actions
This page contains the following MEM actions:
| Button | Description |
| Actions > MEM Assign Entity Security |
Opens the MEM Master Security page where you assign entities to the record. When you select this action, the following header fields on the MEM Master Security are automatically updated as follows and cannot be changed:
|
