TABLE OF CONTENTS

• Introduction
• The use case
• The sending config 
• The receiving config
• Read More

Introduction

This article will guide you through a concrete use case that will help you understand the concept of appending R-Field values from an Activity Code in sending P6 schedule to R-Field in receiving Safran schedule.

The use case

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

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:

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:

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):

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