How to append Safran R-Field values from Activity Code values in P6

Modified on Thu, 9 Oct at 10:14 AM

TABLE OF CONTENTS


Introduction

Just because you have mapped an R-Field in a receiving Safran schedule to an Activity Code (Global or Project specific) in a sending P6 schedule, you cannot expect the values to automatically appear in the receiving R-Field...

This may sound shocking, but has a very simple explanation:

Safran only allows setting values in a receiving R-Field with EXISTING values for that R-Field.

So the question then becomes: 

How can I append values to the R-Field so that they exist and can be set in the receiving schedule?

You have 2 options here:

  1. Do this manually - i.e communicate outside of IDE with the sender so that they only set values that exist in the receiving R-field (and optionally make uploads fail validation if not)
  2. The topic of this article will guide you though a concrete use case that will help you understand how to automatically append missing values to an R-Field.


The use case

Let's say you have a schedule in P6 where you have a global Activity Code (AC) called "Go / No-Go" with values "Y", "N", and "UE". 


A screenshot of a computer

AI-generated content may be incorrect.

Screen for setting up Activity Codes in P6


Let’s also say that you want to pass these values (and descriptions) to R1-Field (Alias "ActionStatus") in Safran having no values to begin with:
A screenshot of a computer

AI-generated content may be incorrect.

Screen for setting up R-Fields in Safran


The sending Config 

In your sending P6 Config (or when editing the IEA based on this Config), you need to specify in a Host System Parameter which AC(s) to upload:

A screenshot of a computer

AI-generated content may be incorrect.

Screen defining the HSP for a sending Config (using a P6 Connector). Here you can select which Activity Codes to send to receiver (and in this example use them to append values in Safran R-Field(s)).


The receiving Config

In the receiving Safran Config (or when editing the IEA based on this config) you need to have the following settings (in red):

A screenshot of a computer

AI-generated content may be incorrect.

Screen defining the HSP for a receiving Config (using a Safran Connector) where one or more structures from the sending schedule is can be "guided" to receiving R-Fields (and missing values will be appended).


Note that you can add as many “Structure to R-Field mappings” as you want by pressing the “+ Add new”-button, and supply the structure name (*), and the R-Field to append values to.
(*) this must be given to you by sender in some form of correspondence – as this is not known by IDE when setting up the receiving config.


Unless you have turned on the Host System Parameter "Allow Append Structures", no values will be appended to the R-Field(s).


Outline codes are not supported to have values appended to them, as it may be ambiguous where in the hierarchy new values should be appended.


Read More

How to append R-Field values from one Safran schedule to another



Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article